View LAN9215_9000206.PDF datasheet online --- IC-ON-LINE

Datasheet File OCR Text:

smsc LAN9215 datasheet revision 2.9 (03-01-12) datasheet product features LAN9215 16-bit non-pci 10/100 ethernet controller with hp auto-mdix support highlights ? optimized for medium performance applications ? efficient architecture with low cpu overhead ? easily interfaces to most 16-bit embedded cpu?s ? integrated phy with hp auto-mdix support ? supports audio & video streaming over ethernet: multiple standard-definiti on (sd) mpeg2 streams ? compatible with other me mbers of lan9218 family target applications ? basic cable, satellite, and ip set-top boxes ? digital video recorders ? video-over ip solutions, ip pbx & video phones ? wireless routers & access points ? audio distribution systems ? printers, kiosks, security systems ? general embedded applications key benefits ? non-pci ethernet controller for medium performance applications ? 16-bit interface ? burst-mode read support ? external mii interface ? eliminates dropped packets ? internal buffer memory can store over 200 packets ? automatic pause and back-pressure flow control ? minimizes cpu overhead ? supports slave-dma ? interrupt pin with programmable hold-off timer ? reduces system cost and in creases design flexibility ? sram-like interface easily interfaces to most embedded cpu?s or soc?s ? reduced power modes ? numerous power management modes ? wake on lan* ? magic packet wakeup* ? wakeup indicator event signal ? link status change ? single chip ethernet controller ? fully compliant with ieee 802.3/802.3u standards ? integrated ethernet mac and phy ? 10base-t and 100base-tx support ? full- and half-duplex support ? full-duplex flow control ? backpressure for half-duplex flow control ? preamble generation and removal ? automatic 32-bit crc generation and checking ? automatic payload padding and pad removal ? loop-back modes ? flexible address filtering modes ? one 48-bit perfect address ? 64 hash-filtered multicast addresses ? pass all multicast ? promiscuous mode ? inverse filtering ? pass all incoming with status report ? disable reception of broadcast packets ? integrated 10/100 ethernet phy ? supports hp auto-mdix ? auto-negotiation ? supports energy-detect power down ? host bus interface ? simple, sram-like interface ? 16-bit data bus ? 16kbyte fifo with flexible tx/rx allocation ? one configurable host interrupt ? miscellaneous features ? low-profile 100-pin tqfp, or 100-ball lfbga lead-free rohs compliant package ? integrated 1.8v regulator ? general purpose timer ? optional eeprom interface ? support for 3 status leds multiplexed with programmable gpio signals ? single 3.3v power supply with 5v tolerant i/o ? 0 c to +70 c commercial temperature support * third-party brands and names are the property of their respective owners.
order number(s): LAN9215-mt for 100-pin, tqfp lead-free rohs compliant package with e3 finish (matte tin) (0 to +70 c temp range) LAN9215-mzp for 100-ball, lfbga lead-free rohs compliant package (0 to +70 c temp range) this product meets the halogen maximum concentration values per iec61249-2-21 for rohs compliance and environmen tal information, please visit www.smsc.com/rohs 16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet revision 2.9 (03-01-12) 2 smsc LAN9215 datasheet copyright ? 2012 smsc or its subsidiaries. all rights reserved. circuit diagrams and other information relating to smsc produc ts are included as a means of illustrating typical applications. consequently, complete information sufficient for construction purposes is not necessarily given. although the information has been checked and is believed to be accurate, no re sponsibility is assumed for inaccuracies. smsc reserves the right to make changes to specifications and produc t descriptions at any time without notice. contact your local sm sc sales office to obtain the latest specifications before placing your product order. the provision of this inform ation does not convey to the purchaser of the described semicond uctor devices any licenses under any patent rights or other intellectual property rights of smsc or others. all sales are expressly conditional on your agreement to the te rms and conditions of the most recently dated version of smsc's standard terms of sale agreement dated before the date of your order (the "terms of sale agreement"). the pro duct may contain design defects or errors known as anomalies which may cause the product's functions to deviate from published specifications. anomaly sheets are availab le upon request. smsc products are not designed, intended, authorized or warranted for use in any life support or other application where product failure could cause or contribute to personal injury or severe property damage. any and all such uses without prior written approval of an officer of smsc and further testing and/or modification will be fully at the risk of the customer. copies of this document or other smsc literature, as well as the terms of sale agreement, may be obtained by visiting smsc?s website at h ttp://www.smsc.com. smsc is a registered trademark of standard microsystems corporation (?smsc?). product names and company names are the trademarks of their respective holders. smsc disclaims and excludes any and all warrant ies, including without limi tation any and all implied warranties of merchantabil ity, fitness for a particular purpose, title, a nd against infringement and the like, and any and all warranties arising from any cou rse of dealing or usage of trade. in no event shall smsc be liable for any direct, incidental, indi rect, special, punitive, or cons equential damages; or for lost data, profits, savings or revenues of any kind; regardless of the form of action, whether based on contrac t; tort; negligence of smsc or others; strict liability; breach of wa rranty; or otherwise; whether or not any remedy of buyer is h eld to have failed of its essential purpose, and whether or not smsc has been advised of the possibility of such damages.
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet smsc LAN9215 3 revision 2.9 (03-01-12) datasheet table of contents chapter 1 general description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 1.1 block diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 1.2 compatibility with first-generation lan9 118 family devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 1.3 internal block overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 1.4 10/100 ethernet phy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 1.5 10/100 ethernet mac . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 1.6 receive and transmit fifos . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 1.7 interrupt controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 1.8 gpio interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 1.9 serial eeprom interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 1.10 power management controls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 1.11 general purpose timer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 1.12 host bus interface (sram interface) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 1.13 external mii interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 chapter 2 pin description and configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 2.1 pin list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 2.2 buffer types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 chapter 3 functional description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 3.1 10/100 ethernet mac . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 3.2 flow control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 3.2.1 full-duplex flow control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 3.2.2 half-duplex flow control (backpressure) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 3.2.3 virtual local area network (vlan) support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 3.3 address filtering functional description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 3.4 filtering modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 3.4.1 perfect filtering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 3.4.2 hash only filtering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 3.5 wake-up frame detection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 3.5.1 magic packet detection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 3.6 host bus operations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 3.6.1 bus writes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 3.6.2 bus reads . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 3.6.3 big and little endian support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 3.6.4 word swap function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 3.7 general purpose timer (gp timer) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 3.8 eeprom interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 3.8.1 mac address auto-load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 3.8.2 eeprom host operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 3.9 power management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 3.9.1 system description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 3.9.2 functional description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 3.9.3 internal phy power-down modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 3.10 detailed reset description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 3.10.1 power-on reset (por) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 5 3.10.2 hardware reset input (nr eset) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 3.10.3 resume reset timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 3.10.4 soft reset (srst) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 3.10.5 phy reset timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 3.11 mii interface - external mii switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet revision 2.9 (03-01-12) 4 smsc LAN9215 datasheet 3.11.1 smi switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 3.11.2 mii clock switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 3.12 tx data path operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 3.12.1 tx buffer format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 3.12.2 tx command format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 1 3.12.3 tx data format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 3.12.4 tx status format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 3.12.5 calculating actual tx data fifo usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 3.12.6 transmit examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 3.12.7 transmitter errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 3.12.8 stopping and starting the transmitter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 3.13 rx data path operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 3.13.1 rx slave pio operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 3.13.2 rx packet format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 3.13.3 rx status format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 3.13.4 stopping and starting the receiver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 3.13.5 receiver errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 chapter 4 internal ethernet phy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 4.1 top level functional description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 4.2 100base-tx transmit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 4.2.1 4b/5b encoding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 4.2.2 scrambling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 4.2.3 nrzi and mlt3 encoding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 4.2.4 100m transmit driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 4.2.5 100m phase lock loop (pll) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 4.3 100base-tx receive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 4.3.1 100m receive input. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 4.3.2 equalizer, baseline wander correction and clock and data recovery . . . . . . . . . . . . . 66 4.3.3 nrzi and mlt-3 decoding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 4.3.4 descrambling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 4.3.5 alignment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 4.3.6 5b/4b decoding. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 4.4 10base-t transmit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 4.4.1 10m transmit data across the internal mii bus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 4.4.2 manchester encoding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 4.4.3 10m transmit drivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 4.5 10base-t receive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 4.5.1 10m receive input and squelch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 4.5.2 manchester decoding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 4.5.3 jabber detection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 4.6 auto-negotiation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 4.7 parallel detection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70 4.7.1 re-starting auto-negotiation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 0 4.7.2 disabling auto-negotiation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70 4.7.3 half vs. full-duplex . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70 4.8 hp auto-mdix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 chapter 5 register description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 5.1 register nomenclature and access attribut es . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 4 5.2 rx and tx fifo ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 5.2.1 rx fifo ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 5.2.2 tx fifo ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 5.3 system control and status registers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet smsc LAN9215 5 revision 2.9 (03-01-12) datasheet 5.3.1 id_rev?chip id and revision . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76 5.3.2 irq_cfg?interrupt configuration register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76 5.3.3 int_sts?interrupt status register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78 5.3.4 int_en?interrupt enable register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80 5.3.5 byte_test?byte order test register. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81 5.3.6 fifo_int?fifo level interr upts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81 5.3.7 rx_cfg?receive configuration register. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82 5.3.8 tx_cfg?transmit configur ation register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83 5.3.9 hw_cfg?hardware configuration register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84 5.3.10 rx_dp_ctrl?receive datapath co ntrol register . . . . . . . . . . . . . . . . . . . . . . . . . . . 87 5.3.11 rx_fifo_inf?receive fifo inform ation register. . . . . . . . . . . . . . . . . . . . . . . . . . . . 88 5.3.12 tx_fifo_inf?transmit fifo info rmation register . . . . . . . . . . . . . . . . . . . . . . . . . . . 88 5.3.13 pmt_ctrl? power management control register . . . . . . . . . . . . . . . . . . . . . . . . . . . 89 5.3.14 gpio_cfg?general purpose io c onfiguration register . . . . . . . . . . . . . . . . . . . . . . . 91 5.3.15 gpt_cfg-general purpose timer configuration regi ster . . . . . . . . . . . . . . . . . . . . . . 92 5.3.16 gpt_cnt-general purpose timer current count re gister . . . . . . . . . . . . . . . . . . . . . . 93 5.3.17 word_swap?word swap control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 5.3.18 free_run?free-run 25mhz counter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94 5.3.19 rx_drop? receiver dropped frames counter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94 5.3.20 mac_csr_cmd ? mac csr synchronizer command register . . . . . . . . . . . . . . . . . 95 5.3.21 mac_csr_data ? mac csr synchronizer data re gister . . . . . . . . . . . . . . . . . . . . . 95 5.3.22 afc_cfg ? automatic flow control configuration register . . . . . . . . . . . . . . . . . . . . . 96 5.3.23 e2p_cmd ? eeprom command register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 5.3.24 e2p_data ? eeprom data register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100 5.4 mac control and status registers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101 5.4.1 mac_cr?mac control register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102 5.4.2 addrh?mac address high register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105 5.4.3 addrl?mac address low register. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106 5.4.4 hashh?multicast hash table high register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107 5.4.5 hashl?multicast hash table low register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107 5.4.6 mii_acc?mii access register. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108 5.4.7 mii_data?mii data register. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108 5.4.8 flow?flow control register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109 5.4.9 vlan1?vlan1 tag register. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110 5.4.10 vlan2?vlan2 tag register. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110 5.4.11 wuff?wake-up frame filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111 5.4.12 wucsr?wake-up control and status register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111 5.5 phy registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112 5.5.1 basic control register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113 5.5.2 basic status register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114 5.5.3 phy identifier 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114 5.5.4 phy identifier 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115 5.5.5 auto-negotiation advertisement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115 5.5.6 auto-negotiation link part ner ability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116 5.5.7 auto-negotiation expansion. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117 5.5.8 mode control/status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117 5.5.9 special modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118 5.5.10 special control/status indications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119 5.5.11 interrupt source flag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120 5.5.12 interrupt mask . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120 5.5.13 phy special control/status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121 chapter 6 timing diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122 6.1 host interface timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet revision 2.9 (03-01-12) 6 smsc LAN9215 datasheet 6.1.1 special restrictions on back-to-back write/read cycles . . . . . . . . . . . . . . . . . . . . . . . 122 6.1.2 special restrictions on back-to-back read cycles . . . . . . . . . . . . . . . . . . . . . . . . . . . 124 6.2 pio reads . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125 6.3 pio burst reads. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126 6.4 rx data fifo direct pio reads . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127 6.5 rx data fifo direct pio burst reads. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128 6.6 pio writes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129 6.7 tx data fifo direct pio writes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130 6.8 reset timing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131 6.9 eeprom timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132 chapter 7 operational characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133 7.1 absolute maximum ratings*. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133 7.2 operating conditions** . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133 7.3 power consumption (device only). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134 7.4 power consumption (device and system components) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135 7.5 worst case current co nsumption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136 7.6 dc electrical specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137 7.7 clock circuit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139 chapter 8 package outline . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140 8.1 100-tqfp package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140 8.2 100-lfbga package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141 chapter 9 datasheet revision history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet smsc LAN9215 7 revision 2.9 (03-01-12) datasheet list of figures figure 1.1 system block diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 figure 1.2 internal block diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 figure 2.1 100-tqfp pin configuration (top view) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 5 figure 2.2 100-lfbga pin configuration (top view) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 figure 3.1 vlan frame . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 figure 3.2 eeprom access flow diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 figure 3.3 eeprom erase cycle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 figure 3.4 eeprom eral cycle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 figure 3.5 eeprom ewds cycle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 figure 3.6 eeprom ewen cycle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 figure 3.7 eeprom read cycle. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 figure 3.8 eeprom write cycle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 figure 3.9 eeprom wral cycle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 figure 3.10 pme and pme_int signal generation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 3 figure 3.11 mii switching procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 figure 3.12 simplified host tx flow diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 figure 3.13 tx buffer format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 figure 3.14 tx example 1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56 figure 3.15 tx example 2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 figure 3.16 host receive routine using interrupts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 figure 3.17 host receive routine with polling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 figure 3.18 rx packet format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 figure 4.1 100base-tx data path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 figure 4.2 receive data path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 figure 4.3 direct cable connection vs. cross-over cable conn ection . . . . . . . . . . . . . . . . . . . . . . . . . 72 figure 5.1 memory map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 figure 5.2 example addrl, addrh and eeprom setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106 figure 6.1 pio read cycle timing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125 figure 6.2 pio burst read cycle timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126 figure 6.3 rx data fifo direct pio read cycle timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127 figure 6.4 rx data fifo direct pio burst read cycle timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128 figure 6.5 pio write cycle timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129 figure 6.6 tx data fifo direct pio write timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 30 figure 6.7 reset timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131 figure 6.8 eeprom timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132 figure 8.1 100 pin tqfp package definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140 figure 8.2 100 ball lfbga package definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141 figure 8.3 100 ball lfbga recommended pcb land pattern . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet revision 2.9 (03-01-12) 8 smsc LAN9215 datasheet list of tables table 2.1 host bus interface signals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 table 2.2 default ethernet settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 table 2.3 lan interface signals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 table 2.4 serial eeprom interface signals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 table 2.5 system and power signals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 table 2.6 mii interface signals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 table 2.7 100-tqfp package pin assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 3 table 2.8 100-lfbga package ball assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 table 2.9 buffer types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 table 3.1 address filtering modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 table 3.2 wake-up frame filter register stru cture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 table 3.3 filter i byte mask bit definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 table 3.4 filter i command bit definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 table 3.5 filter i offset bit definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 table 3.6 filter i crc-16 bit definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 table 3.7 word swap control(16-bit mode only). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 table 3.8 required eeclk cycles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 table 3.9 power management states . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 table 3.10 reset sources and affected circuitry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 table 3.11 tx command 'a' format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 table 3.12 tx command 'b' format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 table 3.13 tx data start offset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 table 4.1 4b/5b code table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 table 4.2 crs behavior . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 table 5.1 direct address register map. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 table 5.2 rx alignment bit definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82 table 5.3 valid tx/rx fifo allocations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86 table 5.4 eeprom enable bit definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 table 5.5 backpressure duration bit mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 table 5.6 mac csr register map. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101 table 5.7 addrl, addrh and eeprom byte ordering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106 table 5.8 LAN9215 phy control and status register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112 table 5.9 mode control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118 table 6.1 read after write timing rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123 table 6.2 read after read timing rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124 table 6.3 pio read timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125 table 6.4 pio burst read timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126 table 6.5 rx data fifo direct pio read timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 7 table 6.6 rx data fifo direct pio burst read cycle timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128 table 6.7 pio write cycle timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129 table 6.8 tx data fifo direct pio write timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130 table 6.9 reset timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131 table 6.10 eeprom timing values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132 table 7.1 power consumption device only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134 table 7.2 power consumption device and system components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135 table 7.3 maximum supply current characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136 table 7.4 i/o buffer characteristics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137 table 7.5 100base-tx transceiver ch aracteristics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138 table 7.6 10base-t transceiver char acteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 38 table 7.7 LAN9215 crystal specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139 table 8.1 100 pin tqfp package parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 0 table 8.2 100 ball lfbga package parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet smsc LAN9215 9 revision 2.9 (03-01-12) datasheet table 9.1 customer revision history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet revision 2.9 (03-01-12) 10 smsc LAN9215 datasheet chapter 1 general description the LAN9215 is a full-featured, single-chip 10/100 ethernet controller designed for embedded applications where performance, flex ibility, ease of integration a nd system cost cont rol are required. the LAN9215 has been architected to provide th e best price-performance ratio for any 16-bit application with medium performance requirements. the LAN9215 is fully ieee 802.3 10base-t and 802.3u 100base-tx compliant, and supports hp auto-mdix. the LAN9215 includes an integrat ed ethernet mac and phy with a high-performance sram-like slave interface. the simple, yet highly functional host bus interface provides a glue-less connection to most common 16-bit microprocessors and microcontrollers as well as 32-bit microprocessors with a 16-bit external bus. the LAN9215 includes large transmit and receive data fifos to accommodate high latency applications. in addition, the LAN9215 memory buffer architecture allows highly efficient use of memory resources by optimizing packet granularity. applications the LAN9215 is well suited for many medi um-performance embedded applications, including: ? printers, kiosks, pos termi nals and security systems ? audio distri bution systems ? general embedded systems ? basic cable, satellite and ip set-top boxes ? voice-over-ip solutions the LAN9215 also supports features which reduce or eliminate packet loss. its internal 16-kbyte sram can hold over 200 received packets. if th e receive fifo gets too full, the LAN9215 can automatically generate flow control packets to the re mote node, or assert back-pressure on the remote node by generating network collisions. the LAN9215 supports numerous power managem ent and wakeup features. the LAN9215 can be placed in a reduced power mode and can be programmed to issue an external wake signal via several methods, including ?magic packet?, ?wake on lan? and ?link status change?. this signal is ideal for triggering system power-up using remote ethernet wakeup events. the device can be removed from the low power state via a host processor command.
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet smsc LAN9215 11 revision 2.9 (03-01-12) datasheet 1.1 block diagram the smsc LAN9215 integrated 10/100 mac/phy controller is a peripher al chip that performs the function of translating parallel data from a host c ontroller into ethernet packets. the LAN9215 ethernet mac/phy controller is designed and optimized to function in an embedded environment. all communication is performed with programmed i/o transactions using the simple sram-like host interface bus. the diagram shown above, describes a typical sys tem configuration of the LAN9215 in a typical embedded environment. the LAN9215 is a general purpose, platform inde pendent, ethernet controller. the LAN9215 consists of four major func tional blocks. the four blocks are: ? 10/100 ethernet phy ? 10/100 ethernet mac ? rx/tx fifos ? host bus interface (hbi) 1.2 compatibility with first-gene ration lan9118 family devices the LAN9215 is driver-, register-, and footprint- compatible with previous generation lan9118 family devices. drivers written for these products will wo rk with the LAN9215. howeve r, in order to support hp auto-mdix, other components such as the magnetics and the passive components around the magnetics need to change, and supporting these changes does require a minor pcb change. a reference design for the LAN9215 will be available on smsc?s website. figure 1.1 system block diagram microprocessor/ microcontroller LAN9215 system peripherals system memory eeprom (optional) 25mhz xtal system bus magnetics ethernet leds/gpio external phy mii magnetics optional optional
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet revision 2.9 (03-01-12) 12 smsc LAN9215 datasheet 1.3 internal block overview this section provides an overview of each of these functional blocks as shown in figure 1.2, "internal block diagram" . figure 1.2 internal block diagram 1.4 10/100 ethernet phy the LAN9215 inte grates an ieee 802.3 ph ysical layer for twisted pair ethernet applicat ions. the phy can be configured for either 100 mbps (100base- tx) or 10 mbps (10base-t) ethernet operation in either full or half duplex configurations. the ph y block supports hp auto-mdix and auto-negotiation. minimal external components are required fo r the utilization of the integrated phy. 1.5 10/100 ethernet mac the transmit and receive data paths are separate within the mac allowing the highest performance especially in full duplex mode. the data paths c onnect to the pio interface function via separate busses to increase performance. payload data as we ll as transmit and receive status is passed on these busses. a third internal bus is used to access the mac?s c ontrol and status register s (csr?s). this bus is accessible from the host through the pio interface function. on the backend, the mac interfac es with the internal 10/100 phy through a mii (media independent interface) port internal to the LAN9215. the mac csr's also provide a mechanism for accessing the phy?s internal registers through the internal smi (serial management interfac e) bus.the ethernet mac can also communicate with an external phy. this mode however, is optional. the mac interface layer (mil), within the mac, cont ains a 2k byte transmit and a 128 byte receive fifo which is separate from the tx and rx fi fos. the fifos within the mac are not directly accessible from the host interface. the different iation between the tx/rx fifo memory buffers and the mac buffers is that when the transmit or receive packets are in the mac buffers, the host no longer 10/100 ethernet mac 2kb to 14kb configurable tx fifo 2kb to 14kb configurable rx fifo interrupt controller gp timer pio controller 3.3v to 1.8v core regulator 25mhz +3.3v eeprom controller eeprom (optional) rx status fifo tx status fifo mil - tx elastic buffer - 2k bytes mil - rx elastic buffer - 128 bytes power management irq fifo_sel pme wakup indicator host bus interface (hbi) 16-bit sram i/f pll +3.3v 3.3v to 1.8v pll regulator 10/100 ethernet phy lan optional external phy - mii interface mux
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet smsc LAN9215 13 revision 2.9 (03-01-12) datasheet can control or access the tx or rx data. the mac buffers (both tx and rx) are in effect the working buffers of the ethernet mac logic. in the case of reception, the data must be moved first to the rx fifos for the host to access the data. for tx operat ions, the mil operates in store-and-forward mode and will queue an entire frame before beginning transmission. 1.6 receive and transmit fifos the receive and transmit fifos allow increased pa cket buffer storage to the mac. the fifos are a conduit between the host interface and the mac th rough which all transmitted and received data and status information is passed. deep fifos allow a high degree of latency tolerance relative to the various transport and os software stacks thus reducing or minimizing overrun conditions. like the mac, the fifos have separate receive and transmit data paths. in addition, the rx and tx fifos are configurable in size, allowing increased flexibility. 1.7 interrupt controller the LAN9215 supports a single programmable interrupt. the programmable nature of this interrupt allows the user the ability to optimize performanc e dependent upon the application requirement. both the polarity and buffer type of the interrupt pin are configurable for the external interrupt processing. the interrupt line can be configured as an open-drain output to facilitate the sharing of interrupts with other devices. in addition, a programmable interrupt de-assertion interval is provided. 1.8 gpio interface a 3-bit gpio and 2-bit gpo (multiplexed on the eepr om and led pins) interf ace is included in the LAN9215. it is accessible through the host bus inte rface via the csrs. the gp io signals can function as inputs, push-pull outputs and open drain outputs. the gpio?s (gpo?s are not configurable) can also be configured to trigger interrupts with programmable polarity. 1.9 serial eeprom interface a serial eeprom interface is in cluded in the la n9215. the serial eeprom is optional and can be programmed with the LAN9215 mac address. the LAN9215 can optionally load the mac address automatically after power-on reset, hardware reset, or soft reset. 1.10 power management controls the LAN9215 supports comprehensive array of pow er management modes to allow use in power sensitive applications. wake on lan, link stat us change and magic packet detection are supported by the LAN9215. an external pme (power managem ent event) interrupt is provided to indicate detection of a wakeup event. 1.11 general purpose timer the general-purpose timer has no dedicated function within the LAN9215 and may be programmed to issue a timed interrupt.
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet revision 2.9 (03-01-12) 14 smsc LAN9215 datasheet 1.12 host bus interf ace (sram interface) the host bus interface provides a fifo interface fo r the transmit and receive data paths, as well as an interface for the LAN9215 control and status registers (csr?s). the host bus interface is the primary bus for connection to the embedded host system. this interface models an asynchronous sram. tx fifo, rx fifo, and csr?s are accessed through this interface. programmed i/o transactions are supported. the LAN9215 host bus interface supports 16-bit bus transfers. internally, all data paths are 32-bits wide. the LAN9215 can be interfaced to either big-endian or little-endian processors. 1.13 external mii interface the LAN9215 also supports the ability to interface to an external phy device. this interface is compatible with all ieee 802.3 mii compliant physical layer devices. fo r additional information on the mii interface and associated signals, please refer to section 3.11, "mii interface - external mii switching," on page 46 for more information.
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet smsc LAN9215 15 revision 2.9 (03-01-12) datasheet chapter 2 pin description and configuration figure 2.1 100-tqfp pin configuration (top view) **denotes a multifunction pin note 1: when hp auto-mdix is activated, the tpo+/- pins function as tpi+/- and vice-versa. 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 50 49 48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32 31 30 29 28 27 26 75 74 73 72 71 70 69 68 67 66 65 64 63 62 61 60 59 58 57 56 55 54 53 52 51 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 gnd_core vreg vdd_core vss_pll xtal2 xtal1 vdd_pll vdd_ref atest rbias vss_ref a7 a6 a5 a4 a3 a2 a1 gnd_io vdd_io tx_en rxd1 rxd2 rxd3 rx_er rxd0 speed_sel amdix_en irq nc pme eeclk** eecs eedio** gnd_core vdd_core d0 d1 d2 vdd_io gnd_io d3 d4 d5 d6 vdd_io gnd_io d7 d8 d9 fifo_sel vss_a (note 1) tpo - (note 1) tpo + vss_a vdd_a (note 1) tpi - (note 1) tpi + nc vdd_a vss_a exres1 vss_a vdd_a nc nc nrd nwr ncs nreset gnd_io vdd_io gpio0/nled1** gpio1/nled2** gpio2/nled3** d10 d11 vdd_io gnd_io d12 d13 d14 d15 vdd_io gnd_io tx_clk txd0 txd1 txd2 txd3 vdd_io gnd_io col crs mdc mdio** rx_dv vdd_io gnd_io rx_clk smsc LAN9215 100 pin tqfp
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet revision 2.9 (03-01-12) 16 smsc LAN9215 datasheet figure 2.2 100-lfbga pin configuration (top view) smsc LAN9215 100-lfbga top view 10 9 8 7 6 5 4 3 2 1 a b c d e f g h j k a b c d e f g h j k 10 9 8 7 6 5 4 3 2 1 l m 11 12 l m vdd_io vdd_io vdd_io vdd_io gnd gnd vdd_io vdd_io vdd_core gnd gnd gnd gnd vdd_core vdd_core gnd gnd gnd gnd vdd_core vdd_io vdd_io gnd gnd vdd_io vdd_io vdd_io vdd_io 11 12 vreg xtal2 xtal1 clkin vdd_pll vdd_ref atest rbias a7 a6 a5 a3 a4 a1 a2 tx_en rxd1 rxd2 rxd3 rx_er rx_clk rx_dv mdio mdc crs col txd3 txd2 txd1 txd0 tx_clk d15 d14 d13 d12 d11 d10 d9 d8 d7 d6 d5 d4 d3 d2 d1 d0 eedio eecs eeclk pme nc irq amdix_en speed_sel rxd0 fifo_sel tpo- tpo+ vdd_a tpi- tpi+ nc vdd_a exres1 vdd_a nrd nwr ncs nreset gpio0 nled1 gpio1 nled2 gpio2 nled3
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet smsc LAN9215 17 revision 2.9 (03-01-12) datasheet 2.1 pin list table 2.1 host bus interface signals name symbol buffer type # pins description host data d[15:0] i/o8 16 bi-directional data port. host address a[7:1] is 7 7-bit address port. used to select internal csr?s and tx and rx fifos. read strobe nrd is 1 active low st robe to indicate a read cycle. write strobe nwr is 1 active low strobe to indicate a write cycle. this signal, qualified with ncs, is also used to wakeup the LAN9215 when it is in a reduced power state. chip select ncs is 1 active low signal used to qualify read and write operations. this signal qualified with nwr is also used to wakeup the LAN9215 when it is in a reduced power state. interrupt request irq o8/od8 1 programmable interrupt request. programmable polarity, source and buffer types. fifo select fifo_sel is 1 when driven high all accesses to the LAN9215 are to the rx or tx data fifos. in this mode, the a[7:3] upper address inputs are ignored. table 2.2 default ethernet settings default ethernet settings speed_sel speed duplex auto neg. 0 10mbps half-duplex disabled 1 100mbps half-duplex enabled table 2.3 lan interface signals name symbol buffer type num pins description tpo+ tpo+ ao 1 transmit positive output (normal) receive positive input (reversed) tpo- tpo- ao 1 transmit negative output (normal) receive negative input (reversed) tpi+ tpi+ ai 1 receive positive input (normal) transmit positive input (reversed) tpi- tpi- ai 1 receive negative input (normal) transmit negative output (reversed) phy external bias resistor exres1 ai 1 must be connected to ground through a 12.4k ohm 1% resistor.
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet revision 2.9 (03-01-12) 18 smsc LAN9215 datasheet note: the pin names for the twisted pair pins shown ab ove apply to a normal connection. if hp auto- mdix is enabled and a reverse connection is detected, or a revers e connection is manually selected, the input pins become outputs, and vice-versa, as indicated in the descriptions. table 2.4 serial eeprom interface signals name symbol buffer type num pins description eeprom data, gpo3, tx_en, tx_clk eedio/gpo3/ tx_en/tx_clk i/o8 1 eeprom data: this bi-directional pin can be connected to a serial eeprom dio. this is optional. general purpose output 3: this pin can also function as a general purpose output, or it can be configured to monitor the tx_en or tx_clk signals on the internal mii port. when configured as a gpo signal, or as a tx_en/tx_clk monitor, the eecs pin is deasserted so as to never unintentionally access the serial eeprom. this signal cannot function as a general-purpose input. eeprom chip select eecs o8 1 serial eeprom chip select. eeprom clock, gpo4 rx_dv, rx_clk eeclk/gpo4/ rx_dv/rx_clk o8 1 eeprom clock: serial eeprom clock pin. general purpose output 4: this pin can also function as a general-purpose output, or it can be configured to monitor the rx_dv or rx_clk signals on the internal mii port. when configured as a gpo signal, or as an rx_dv/rx_clk monitor, the eecs pin is deasserted so as to never unintentionally access the serial eeprom. this signal cannot function as a general-purpose input. note: when the eeprom interface is not used, the eeclk pin must be left unconnected.
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet smsc LAN9215 19 revision 2.9 (03-01-12) datasheet table 2.5 system and power signals name symbol buffer type num pins description crystal 1, clock in xtal1/clkin lclk 1 external 25mhz crystal input. this pin can also be connected to single-ended ttl oscillator (clkin). if this method is implemented, xtal2 should be left unconnected. crystal 2 xtal2 oclk 1 exter nal 25mhz crystal output. reset nreset is (pu) 1 active-low reset input. resets all logic and registers within the LAN9215. this signal is pulled high with a weak internal pull-up resistor. if nreset is left unconnected, the LAN9215 will rely on its internal power-on reset circuitry. note: the LAN9215 must always be read at least once after power-up, reset, or upon return from a power-saving state or write operations will not function. see section 3.10, "detailed reset description," on page 44 for additional information wakeup indicator pme o8/od8 1 when programmed to do so, is asserted when the LAN9215 detects a wake event and is requesting the system to wake up from the associated sleep state. the polarity and buffer type of this signal is programmable. note: detection of a power management event, and assertion of the pme signal will not wakeup the LAN9215. the LAN9215will only wake up when it detects a host write cycle (assertion of ncs and nwr). although any write to the LAN9215, regardless of the data written, will wake- up the device when it is in a power-saving mode, it is required that the byte_test register be used for this purpose. auto-mdix enable amdix_en i (pd) 1 enables auto-mdix. pull high enable auto- mdix, pull low or leave unconnected to disable auto-mdix. 10/100 selector speed_sel i (pu) 1 this signal functions as a configuration input on power-up and is used to select the default ethernet settings. upon deassertion of reset, the value of the input is latched. this signal functions as shown in table 2.2, "default ethernet settings" , below. no connect nc 4 no connect. these pins must be left open.
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet revision 2.9 (03-01-12) 20 smsc LAN9215 datasheet general purpose i/o data, nled1 (speed indicator), nled2 (link & activity indicator), nled3 (full- duplex indicator ) . gpio[2:0]/ nled[3:1] is/o12/ od12 3 general purpose i/o data: these three general-purpose signals are fully programmable as either push-pull outpu t, open-drain output or input by writing the gpio_cfg configuration register in the csr?s. they are also multiplexed as gp led connections. gpio signals are schmitt-triggered inputs. when configured as led outputs these signals are open-drain. nled1 (speed indicator). this signal is driven low when the operating speed is 100mb. during auto-negotiation, when the cable is disconnected, and during 10mbs operation, this signal is driven high. nled2 (link & activity indicator). this signal is driven low (led on) when the LAN9215 detects a valid link. this signal is pulsed high (led off) for 80ms whenever transmit or receive activity is detect ed. this signal is then driven low again for a minimum of 80ms, after which time it will repeat the process if tx or rx activity is detected. effectively, led2 is activated solid for a link. when transmit or receive activity is sensed led2 will flash as an activity indicator. nled3 (full-duplex indicator). this signal is driven low when the link is operating in full- duplex mode. rbias rbias ai 1 pll bias: connect to an external 12.0k ohm 1.0% resistor to ground. used for the pll bias circuit. te s t p i n at e s t i 1 this pin must be connected to vdd for normal operation. internal regulator power vreg p 1 3.3v input for internal voltage regulator +3.3v i/o power vdd_io p 8 +3.3v i/o logic power supply pins i/o ground gnd_io p 8 ground for i/o pins (100-tqfp package only) +3.3v analog power vdd_a p 3 +3.3v analog power supply pins. see note 2.1 . analog ground vss_a p 4 ground for analog circuitry (100-tqfp package only) core voltage decoupling vdd_core p 2 +1.8 v from internal core regulator. both pins must be connected toge ther externally. each pin requires a 0.01uf decoupling capacitor. in addition, pin 3 requires a bulk 10uf capacitor (<2 ohm esr) in parallel. these pins must not be used to supply power to other external devices. see note 2.1 . core ground gnd_core p 2 ground for internal digital logic (100-tqfp package only) table 2.5 system and power signals (continued) name symbol buffer type num pins description
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet smsc LAN9215 21 revision 2.9 (03-01-12) datasheet note 2.1 please refer to the smsc application note ?a n14.9 - ?migrating from lan9115 to the LAN9215? for additional details. pll power vdd_pll p 1 +1.8v power from the internal pll regulator. this pin must be connected to a 10uf capacitor (<2 ohm esr), in parallel with a 0.01uf capacitor to ground. this pin must not be used to supply power to other external devices. see note 2.1 . pll ground vss_pll p 1 gnd for the pll (100-tqfp package only) reference power vdd_ref p 1 connected to 3.3v power and used as the reference voltage for the internal pll reference ground vss_ref p 1 ground fo r internal pll reference voltage (100-tqfp package only) ground gnd p 12 common ground (100-lfbga package only) table 2.6 mii interface signals name symbol buffer type num pins description transmit clock: tx_clk i (pd) 1 transmit clock : 25mhz in 100base-tx mode. 2.5mhz in 10base-t mode. transmit data [3:0] txd[3:0] o8 (pd) 4 transmit data 3-0 : data bits that are accepted by the phy for transmission. when the internal phy is selected, these signals are driven low (0). transmit enable tx_en o8 (pd) 1 transmit enable : indicates that valid data is presented on the txd[3:0] signals, for transmission. when the internal phy is selected, this signal is driven low (0). receive clock rx_clk i (pd) 1 receive clock : 25mhz in 100base-tx mode. 2.5mhz in 10base-t mode. receive error rx_er i (pd) 1 receive error : asserted by the phy to indicate that an error was detected somewhere in the frame presently being transferred from the phy. collision detect: col i (pd) 1 mii collision detect : asserted by the phy to indicate detection of collision condition. receive data[3:0] rxd[3:0] i note 2.2 1 receive data 3-0 : data bits that are sent from the phy to the ethernet mac. see note 2.2 . carrier sense crs i (pd) 1 carrier sense : indicates detection of carrier. receive data valid: rx_dv i (pd) 1 receive data valid : indicates that recovered and decoded data nibbles are being presented by the phy on rxd[3:0]. table 2.5 system and power signals (continued) name symbol buffer type num pins description
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet revision 2.9 (03-01-12) 22 smsc LAN9215 datasheet note 2.2 pins rxd[3:1] provide internal pull-down resist ors to prevent these pins from floating when unused. rxd0 (pin 75) does not provide an in ternal pull-down resistor. this pin must be pulled or driven to a valid state at all times. note 2.3 the external smi port is selected when smi_sel = 1. when smi_sel = 0, mdio is tri- stated and mdc is driven low. management data io/external phy detect mdio (ext_phy_det) i/o8 (pd) 1 management data io: when smi_sel = 1, this pin is the mii smi serial io bus pin. external phy detect: this pin also functions as a strap input, which can be used to indicate the presence of an external phy. note: see section 5.3.9, "hw_cfg?hardware configuration register" for more information on smi_sel and ext_phy_det management data clock mdc o8 (pd) 1 management data clock: when smi_sel = 1, this pin is the mii management data clock. when smi_sel=0, this pin is driven low. note: see section 5.3.9, "hw_cfg?hardware configuration register" for more information on smi_sel. table 2.6 mii interface signals name symbol buffer type num pins description
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet smsc LAN9215 23 revision 2.9 (03-01-12) datasheet table 2.7 100-tqfp package pin assignments pin num pin name pin num pin name pin num pin name pin num pin name 1 gnd_core 26 rx_clk 51 d9 76 fifo_sel 2 vreg 27 gnd_io 52 d8 77 vss_a 3 vdd_core 28 vdd_io 53 d7 78 tpo- 4 vss_pll 29 rx_dv 54 gnd_io 79 tpo+ 5 xtal2 30 mdio 55 vdd_io 80 vss_a 6 xtal1 31 mdc 56 d6 81 vdd_a 7 vdd_pll 32 crs 57 d5 82 tpi- 8 vdd_ref 33 col 58 d4 83 tpi+ 9 atest 34 gnd_io 59 d3 84 nc 10 rbias 35 vdd_io 60 gnd_io 85 vdd_a 11 vss_ref 36 txd3 61 vdd_io 86 vss_a 12 a7 37 txd2 62 d2 87 exres1 13 a6 38 txd1 63 d1 88 vss_a 14 a5 39 txd0 64 d0 89 vdd_a 15 a4 40 tx_clk 65 vdd_core 90 nc 16 a3 41 gnd_io 66 gnd_core 91 nc 17 a2 42 vdd_io 67 eedio 92 nrd 18 a1 43 d15 68 eecs 93 nwr 19 gnd_io 44 d14 69 eeclk 94 ncs 20 vdd_io 45 d13 70 pme 95 nreset 21 tx_en 46 d12 71 nc 96 gnd_io 22 rxd1 47 gnd_io 72 irq 97 vdd_io 23 rxd2 48 vdd_io 73 amdix_en 98 gpio0/nled1 24 rxd3 49 d11 74 speed_sel 99 gpio1/nled2 25 rx_er 50 d10 75 rxd0 100 gpio2/nled3
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet revision 2.9 (03-01-12) 24 smsc LAN9215 datasheet table 2.8 100-lfbga package ball assignments pin num pin name pin num pin name pin num pin name pin num pin name a1 vreg c2 vdd_pll g1 a4 k12 d5 a2 gpio2/nled3 c3 vdd_io g2 a3 l1 rxd3 a3 gpio0/nled1 c10 vdd_io g5 gnd l2 rx_er a4 nreset c11 amdix_en g8 gnd l3 mdio a5 nwr c12 irq g11 d1 l4 vdd_io a6 vdd_a d1 atest g12 d0 l5 col a7 exres1 d2 vdd_io h1 a2 l6 txd2 a8 tpi+ d3 vdd_core h2 a1 l7 tx_clk a9 tpi- d10 vdd_core h5 gnd l8 d14 a10 tpo+ d11 vdd_io h6 gnd l9 vdd_io a11 tpo- d12 nc h7 gnd l10 d11 a12 fifo_sel e1 a7 h8 gnd l11 d8 b1 xtal1/clkin e2 rbias h11 d3 l12 d7 b2 xtal2 e5 gnd h12 d2 m1 rx_clk b3 gpio1/nled2 e6 gnd j1 tx_en m2 rx_dv b4 vdd_io e7 gnd j2 vdd_io m3 mdc b5 ncs e8 gnd j3 vdd_core m4 crs b6 nrd e11 pme j10 vdd_core m5 txd3 b7 vdd_a e12 eeclk j11 vdd_io m6 txd1 b8 nc f1 a5 j12 d4 m7 txd0 b9 vdd_io f2 a6 k1 rxd1 m8 d15 b10 vdd_a f5 gnd k2 rxd2 m9 d13 b11 rxd0 f8 gnd k3 vdd_io m10 d12 b12 speed_sel f11 eecs k10 vdd_io m11 d10 c1 vdd_ref f12 eedio k11 d6 m12 d9
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet smsc LAN9215 25 revision 2.9 (03-01-12) datasheet 2.2 buffer types note 2.4 table 2.9 buffer types type description i input pin is schmitt triggered input o12 output with 12ma sink and 12ma source od12 open-drain output with 12ma sink od8 open-drain output with 8ma sink o8 output 8ma symmetrical drive pu 50ua (typical) internal pull-up pd 50ua (typical) internal pull-down ai analog input ao analog output aio analog bi-directional iclk crystal oscillator input pin oclk crystal oscillator output pin
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet revision 2.9 (03-01-12) 26 smsc LAN9215 datasheet chapter 3 functional description 3.1 10/100 ethernet mac the ethernet media access controll er (mac) incorporates the essential protocol requirements for operating an ethernet/ieee 802.3-compliant node and provides an inte rface between the host subsystem and the internal ethernet phy. the mac can operate in either 100-mbps or 10-mbps mode. the mac operates in both half-duplex and full- duplex modes. when operating in half-duplex mode, the mac complies fully with section 4 of iso/iec 8802-3 (ansi/ieee standard) and ansi/ieee 802.3 standards. when operating in full-duplex mode, the mac complies with ieee 802.3x full-duplex operation standard. the mac provides programmable enhanced features designed to mi nimize host supervision, bus utilization, and pre- or post-message processing. these features incl ude the ability to disable retries after a collision, dynamic fcs (frame check sequence) generation on a frame-by-frame basis, automatic pad field insertion and deletion to enforce minimum frame size attributes, and automatic retransmission and detection of collision frames. the mac can sustain transmission or reception of minimally-sized ba ck-to-back packets at full line speed with an interpacket gap (ipg) of 9.6 microseconds for 10 mbps and 0.96 microseconds for 100 mbps. the primary attributes of the mac function are: ? transmit and receive message data encapsulation ? framing (frame boundary delimitation, frame synchronization) ? error detection (physical medium transmission errors) ? media access management ? medium allocation (collision detectio n, except in full-duplex operation) ? contention resolution (collision handling, except in full-duplex operation) ? flow control during full-duplex mode ? decoding of control frames (pause command) and disabling the transmitter ? generation of control frames ? interface to the internal phyand optional external phy. the transmit and receive data paths are separate within the LAN9215 from the mac to host interface allowing the highest performance, especially in fu ll duplex mode. payload data as well as transmit and receive status are passed on these busses. a third internal bus is used to access the mac?s ?c ontrol and status registers? (csr?s). this bus is also accessible from the host. on the backend, the mac interfaces with the 10/100 phy through an mii (media independent interface) port which is internal to the LAN9215. in addition, there is an external mii interface supporting optional phy devices.the mac csr's also provide a mechanism for accessing the phy?s internal registers through the internal smi (serial management interface) bus. the receive and transmit fifos allow increased pa cket buffer storage to the mac. the fifos are a conduit between the host interface and the mac th rough which all transmitted and received data and status information is passed. deep fifos allow a high degree of latency tolerance relative to the various transport and os software stacks reducing and minimizing overrun conditions. like the mac, the fifos have separate receive and transmit data paths.
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet smsc LAN9215 27 revision 2.9 (03-01-12) datasheet the LAN9215 can store up to 250 ethernet packets ut ilizing fifos, totaling 16k bytes, with a packet granularity of 4 bytes. this memory is shared by the rx and tx blocks and is configurable in terms of allocation. this depth of buffer storage minimizes or eliminates receive overruns. 3.2 flow control the LAN9215 ethernet mac supports full-duplex flow control using the pause operation and control frame. it also supports half-duplex flow control using back pressure. 3.2.1 full-duplex flow control the pause operation inhibits data transmission of data frames for a specified period of time. a pause operation consists of a frame containing the global ly assigned multicast address (01-80-c2-00-00-01), the pause opcode, and a parameter indicating the quantum of slot time (512 bit times) to inhibit data transmissions. the pause parameter may range from 0 to 65,535 slot times. the ethernet mac logic, on receiving a frame with the re served multicast address and paus e opcode, inhibits data frame transmissions for the length of ti me indicated. if a pause request is received while a transmission is in progress, then the pause will take effect after the transmission is complete. control frames are received and processed by the mac and are passed on. the mac also transmits control frames (pause comm and) via both hardware and software control. the software driver requests the mac to transmit a control frame and gives the value of the pause time to be used in the control frame. the mac functi on constructs a control fr ame with the appropriate values set in all the different fields (as defined in the 802.3x specification) and transmits the frame to the mii interface. the transmission of the control fram e is not affected by the current state of the pause timer value that is set because of a recently received control frame. 3.2.2 half-duplex flow control (backpressure) in half-duplex mode, back pressure is used for flow control. whenever the receive buffer/fifo becomes full or crosses a certain threshold level, the mac starts sending a jam signal. the mac transmit logic enters a state at the end of current transmission (if an y), where it waits for the beginning of a received frame. once a new frame starts, the mac starts sending the jam signal, which will result in a collision. after sensing the collision, the remote station will back off its transmission. the mac continues sending the jam to make other stations defer transmission. the mac only generates this collision-based back pressure when it receives a new frame, in order to avoid any late collisions. 3.2.3 virtual local area network (vlan) support virtual local area networks or vlans, as defined within the ieee 802.3 standard, provide network administrators one means of group ing nodes within a larger netwo rk into broadcast domains. to implement a vlan, four extra bytes are added to the basic ethernet packet. as shown in figure 3.1, "vlan frame" , the four bytes are inserted after the sour ce address field and before the type/length field. the first two bytes of the vlan tag identif y the tag, and by convention are set to the value 0x8100. the last two bytes identify the specific vlan associated with the packet; they also provide a priority field. the LAN9215 supports vlan-tagged packets. the LAN9215 provides two registers which are used to identify vlan-tagged packets. one register should normally be set to the conventional vlan id of 0x8100. the other register provides a way of identifying vlan frames tagged with a proprietary (not 0x8100) identifier. if a packet arrives bearing eith er of these tags in the two bytes succeeding the source address field, the controller will recognize the packet as a vlan-tagged packet. in this case, the controller increases the maximum allowed packet size from 1518 to 1522 bytes (normally the controller filters packets larger than 1518 bytes). this allows the packet to be received, and then processed by host software, or to be transmitted on the network.
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet revision 2.9 (03-01-12) 28 smsc LAN9215 datasheet 3.3 address filtering functional description the ethernet address fields of an ethernet packet, consists of two 6-byte fields: one for the destination address and one for the source address. the first bi t of the destination address signifies whether it is a physical address or a multicast address. the LAN9215 address check logic filters the frame ba sed on the ethernet rece ive filter mode that has been enabled. filter modes ar e specified based on the state of the control bits in table 3.1, "address filtering modes" , which shows the various filtering modes us ed by the ethernet mac function. these bits are defined in more detail in the ?mac control register?. please refer to section 5.4.1, "mac_cr?mac control register" for more information on this register. if the frame fails the filter, the ethernet mac function does not rece ive the packet. the host has the option of accepting or ignoring the packet. figure 3.1 vlan frame table 3.1 address filtering modes mcpas prms invfilt ho hpfilt description 0 0 0 0 0 mac address perfect filtering only for all addresses. 0 0 0 0 1 mac address perfect filtering for physical address and hash filtering for multicast addresses
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet smsc LAN9215 29 revision 2.9 (03-01-12) datasheet 3.4 filtering modes 3.4.1 perfect filtering this filtering mode passes only in coming frames whose destination address field exactly matches the value programmed into the mac address high regi ster and the mac address low register. the mac address is formed by the concatenation of the above two registers in the mac csr function. 3.4.2 hash only filtering this type of filtering checks for incoming receive packets with either multicast or physical destination addresses, and executes an imperfect addr ess filtering against the hash table. during imperfect hash filtering, the destination address in the incoming frame is passed through the crc logic and the upper six bits of the crc register are used to index the contents of the hash table. the hash table is formed by merging the register?s multicast hash table high and multicast hash table low in the mac csr function to form a 64-bit hash table. the most significant bit determines the register to be used (high/low), while the other five bits determine the bit within the register. a value of 00000 selects bit 0 of the multicast hash table low register and a value of 11111 selects bit 31 of the multicast hash table high register. 3.4.2.1 hash perfect filtering in hash perfect filtering, if the received frame is a physical address, the LAN9215 packet filter block perfect-filters the incoming frame?s destination fi eld with the value programmed into the mac address high register and the mac address low register. if the incoming frame is a multicast frame, however, the LAN9215 packet filter function performs an imperfect address filtering against the hash table. the imperfect filtering again st the hash table is the same imperfe ct filtering process described in the ?hash only filtering? section above. 3.4.2.2 inverse filtering in inverse filtering, the packet filter block accepts incoming frames with a destination address not matching the perfect address (i.e., the value progr ammed into the mac address high register and the mac address low register in the crc block and re jects frames with destination addresses matching the perfect address). for all filtering modes, when the mcpas bit is set, all multicast frames are accepted. when the prms bit is set, all frames are accepted regardless of th eir destination address. this includes all broadcast frames as well. 0 0 0 1 1 hash filtering for physical and multicast addresses 0 0 1 0 0 inverse filtering x 1 0 x x promiscuous 1 0 0 0 x pass all multicast frames. frames with physical addresses are perfect-filtered 1 0 0 1 1 pass all multicast frames. frames with physical addresses are hash- filtered table 3.1 address filtering modes (continued) mcpas prms invfilt ho hpfilt description
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet revision 2.9 (03-01-12) 30 smsc LAN9215 datasheet 3.5 wake-up frame detection setting the wake-up frame enable bit (wuen) in the ?wucsr?wake-up control and status register?, places the LAN9215 mac in the wake- up frame detection mode. in this mode, normal data reception is disabled, and detection logic withi n the mac examines receive data for the pre- programmed wake-up frame patter ns. the LAN9215 can be programm ed to notify the host of the wake-up frame detection with the asse rtion of the host interrupt (i rq) or assertion of the power management event signal (pme). u pon detection, the wake-up frame received bit (wufr) in the wucsr is set. when the host clears the wuen bit the LAN9215 will resume normal receive operation. before putting the mac into the wake-up frame dete ction state, the host must provide the detection logic with a list of sample frames and their corresponding byte masks. this information is written into the wake-up frame filter register (wuff). please refer to section 5.4.11, "wuff?wake-up frame filter," on page 111 for additional information on this register. the mac supports four programmable filters that su pport many different receive packet patterns. if remote wake-up mode is enabled, the remote wake-up function receives all frames addressed to the mac. it then checks each frame against the enabled filter and recognizes the frame as a remote wake- up frame if it passes the wakeup frame filter register?s address filtering and crc value match. in order to determine which bytes of the frames should be checked by the crc module, the mac uses a programmable byte mask and a programmable pattern offset for each of the four supported filters. the pattern?s offset defines the location of the firs t byte that should be che cked in the frame. since the destination address is checked by the address filtering function, t he pattern offset is always greater than 12. the byte mask is a 31-bit field that specifies whet her or not each of the 31 contiguous bytes within the frame, beginning in the pattern offset, should be checked. if bit j in the byte mask is set, the detection logic checks byte offset +j in the frame. in order to load the wake-up frame filter register, the host lan driver software must perform eight wr ites to the wake-up frame filter register (wuff). the diagram shown in table 3.2, "wake-up frame filter register structure" below, shows the wake- up frame filter register?s structure. note 3.1 wake-up frame detection can be performed when the LAN9215 is in the d0 or d1 power states. in the d0 state, wake-up frame detec tion is enabled when the wuen bit is set. note 3.2 wake-up frame detection, as well as magi c packet detection, is always enabled and cannot be disabled when the device enters the d1 state. note 3.3 when wake-up frame detection is enabled via the wuen bit of the wucsr?wake-up control and status register , a broadcast wake-up frame wil l wake-up the device despite the state of the disable broadcast frame (bcast) bit in the mac_cr?mac control register .
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet smsc LAN9215 31 revision 2.9 (03-01-12) datasheet the filter i byte mask defines which incoming fram e bytes filter i will examine to determine whether or not this is a wake-up frame. ta b l e 3 . 3 , describes the byte mask?s bit fields. the filter i command register controls filter i operation. table 3.4 shows the filter i command register. the filter i offset register defi nes the offset in the frame?s desti nation address field from which the frames are examined by filter i. ta b l e 3 . 5 describes the filter i offset bit fields. table 3.2 wake-up frame fi lter register structure filter 0 byte mask filter 1 byte mask filter 2 byte mask filter 3 byte mask reserved filter 3 command reserved filter 2 command reserved filter 1 command reserved filter 0 command filter 3 offset filter 2 offset filter 1offset filter 0 offset filter 1 crc-16 filter 0 crc-16 filter 3 crc-16 filter 2 crc-16 table 3.3 filter i byte mask bit definitions filter i byte mask description field description 31 must be zero (0) 30:0 byte mask: if bit j of the byte mask is set, the crc machine processes byte number pattern - (offset + j) of the incoming frame. otherwise, byte pattern - (offset + j) is ignored. table 3.4 filter i co mmand bit definitions filter i commands field description 3 address type: defines the destination address type of the pattern. when bit is set, the pattern applies only to multicast frames. when bit is cleared, the pattern applies only to unicast frames. 2:1 reserved 0 enable filter: when bit is set, filter i is enabled, otherwise, filter i is disabled.
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet revision 2.9 (03-01-12) 32 smsc LAN9215 datasheet the filter i crc-16 register cont ains the crc-16 result of the fr ame that should pass filter i. table 3.6 describes the filter i crc-16 bit fields. 3.5.1 magic packet detection setting the magic packet enable bit (mpen) in the ?wucsr?wake-up control and status register?, places the LAN9215 mac in the ?magic packet? detec tion mode. in this mode , normal data reception is disabled, and detection logic within the mac examines receive data for a magic packet. the LAN9215 can be programmed to notify the host of the ?magic packet? detection with the assertion of the host interrupt (irq) or assertion of the po wer management event signal (pme). upon detection, the magic packet received bit (mpr) in the wucsr is set. when the host clears the mpen bit the LAN9215 will resume normal receive operation. please refer to section 5.4.12, "wucsr?wake-up control and status register," on page 111 for additional information on this register in magic packet mode, the power management logic constantly monitors each frame addressed to the node for a specific magic packet pattern. it checks only packets with the mac?s address or a broadcast address to meet the magic packet requ irement. the power management logic checks each received frame for the pattern 48h ff_ff_ff_ff_ff_ff after the destination and source address field. then the function looks in the frame for 16 repetitions of the mac address without any breaks or interruptions. in case of a break in the 16 addr ess repetitions, the pmt function scans for the 48'hff_ff_ff_ff_ff_ff pattern again in the incoming frame. the 16 repetitions may be anywhere in the frame but must be preceded by the synchronization stream. the device will also accept a multicast frame, as l ong as it detects the 16 duplications of the mac address. if the mac address of a node is 00h 11h 22h 33h 44h 55h, then the mac scans for the following data sequence in an ethernet: frame. table 3.5 filter i offset bit definitions filter i offset description field description 7:0 pattern offset: the offset of the first byte in the fram e on which crc is checked for wake-up frame recognition. the minimum value of this field mu st be 12 since there should be no crc check for the destination address and the sour ce address fields. th e mac checks the first offset byte of the frame for crc and checks to determine whether the fr ame is a wake-up frame. offset 0 is the first byte of the incoming frame's destination address. table 3.6 filter i crc-16 bit definitions filter i crc-16 description field description 15:0 pattern crc-16: this field contains the 16-bit crc value from the pattern and the byte mask programmed to the wake-up filter register function. this val ue is compared against the crc calculated on the incoming frame, and a matc h indicates the reception of a wakeup frame.
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet smsc LAN9215 33 revision 2.9 (03-01-12) datasheet destination address source ad dress ?????ff ff ff ff ff ff 00 11 22 33 44 55 00 11 22 33 44 55 00 11 22 33 44 55 00 11 22 33 44 55 00 11 22 33 44 55 00 11 22 33 44 55 00 11 22 33 44 55 00 11 22 33 44 55 00 11 22 33 44 55 00 11 22 33 44 55 00 11 22 33 44 55 00 11 22 33 44 55 00 11 22 33 44 55 00 11 22 33 44 55 00 11 22 33 44 55 00 11 22 33 44 55 ?crc it should be noted that magic packet detection can be performed when LAN9215 is in the d0 or d1 power states. in the d0 st ate, ?magic packet? detection is enabled when the mpen bit is set. in the d1 state, magic packet detection, as well as wa ke-up frame detection, ar e automatically enabled when the device enters the d1 state. 3.6 host bus operations 3.6.1 bus writes the host processor is required to perform two c ontiguous 16-bit writes to complete a single dword transfer. this dword must begin and end on a dword address boundary (a[2] and higher, cannot change during a sixteen bit write). no ordering r equirements exist. the processor can access either the low or high word first, as long as the next writ e is performed to the other word. if a write to the same word is performed, the la n9215 disregards the transfer. 3.6.2 bus reads the host processor is required to perform two cons ecutive 16-bit reads to complete a single dword transfer. this dword must begin and end on a dword address boundary (a[2] and higher, cannot change during a sixteen bit read). no ordering requ irements exist. the processor can access either the low or high word first, as long as the next re ad is performed from the other word. if a read to the same word is performed, the data read is invalid and should be re-read. this is not a fatal error. the LAN9215 will reset its read counters and restar t a new cycle on the next read. 3.6.3 big and litt le endian support the LAN9215 supports ?big-? or ?little-endian? proce ssors with either 16 or 32-bit busses. to support big-endian processors, the hardware designer must ex plicitly invert the layout of the byte lanes. 3.6.4 word swap function internally the LAN9215 is 32-bits wide. the LAN9215 supports a word swap function. this feature is controlled by the word swap register, which is described in section 5.3.17, "word_swap?word swap control," on page 93 . this register affects how words on the data bus are written to or read from the control and status registers and the transmit and receive data/status fifos. refer to ta b l e 3 . 7 , "word swap control(16-bit mode only)" below for more details. whenever the LAN9215 transmits data from the transmit data fifo to the network, the low order word is always transmitted first, and when the LAN9215 receives data from the network to the receive data fifo, the low-order word is always received first. .
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet revision 2.9 (03-01-12) 34 smsc LAN9215 datasheet 3.7 general purpose timer (gp timer) the general purpose timer is a programmable block that can be used to generate periodic host interrupts. the resolution of this timer is 100us. the gp timer loads the gpt_cnt register with the value in the gpt_load field and begins counting down when the timer_en bit is set to a ?1.? on a reset, or when the timer_en bit changes from set ?1? to cleared ?0,? the gpt_load field is initialized to ffffh. the gpt_cnt register is also initialized to ffffh on a reset. software can writ e the pre-load value into the gpt_load field at any time; e.g., before or after the timer_en bit is asserted. the gpt enable bit timer_en is located in the gpt_cfg register. once enabled, the gpt counts down either until it reaches 0000h or until a new pre-load value is written to the gpt_load field. at 0000h, the counter wraps around to ffffh, asserts the gpt interrupt status bit and the irq signal if the gpt_int_en bit is set, and continues counting. the gpt interrupt status bit is in the int_sts register. the gpt_int hardware interrupt can only be set if the gpt_int_en bit is set. gpt_int is a sticky bit (r/wc); i.e., once t he gpt_int bit is set, it can only be cleared by writing a ?1? to the bit. 3.8 eeprom interface the LAN9215 can optionally load its mac address from an external serial eeprom. if a properly configured eeprom is detected by the LAN9215 at power-up, hard reset or soft reset, the addrh and addrl registers will be loaded with the contents of the eeprom. if a properly configured eeprom is not detected, it is the responsibility of the host lan driver to set the ieee addresses. the LAN9215 eeprom controller al so allows the host system to read, write and erase the contents of the serial eeprom. the eeprom controller sup ports most ?93c46? type eeproms configured for 128 x 8-bit operation. table 3.7 word swap control(16-bit mode only) address a1 pin byte order description d[15:8] d[7:0] default mode - word swap register equal to 0x00000000 or any value other than 0xffffffff a1 = 0 byte 1 byte 0 when a1=0, the data bus is mapped to the low order words of csrs and fifos. when a1=1, the data bus is mapped to the high-order words of csrs and fifos. since low-order words are always transmitted/received first, a1=0 data will always precede a1=1 data. a1 = 1 byte 3 byte 2 word swap mode - word swap register equal to 0xffffffff a1 = 0 byte 3 byte 2 when a1=0, the data bus is mapped to the high order words of csrs and fifos. when a1=1, the data bus is mapped to the low order words of csrs and fifos. in this case a1=1 data will always precede a1=0 data. a1 = 1 byte 1 byte 0
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet smsc LAN9215 35 revision 2.9 (03-01-12) datasheet 3.8.1 mac address auto-load on power-up, hard reset or soft reset, the eeprom controller attempts to read the first byte of data from the eeprom (address 00h). if the value a5 h is read from the first address, then the eeprom controller will assume that an external serial e eprom is present. the eepr om controller will then access the next eeprom byte and send it to the mac address register by te 0 (addrl[7:0]). this process will be repeated for the next five bytes of the mac address, thus fully programming the 48- bit mac address. once all six bytes have been programmed, the ?mac address loaded? bit is set in the e2p_cmd register. a detailed explanation of th e eeprom byte ordering with respect to the mac address is given in section 5.4.3, "addrl?mac address low register," on page 106 . if an 0xa5h is not read from the first address, th e eeprom controller will end initialization. it is then the responsibility of the host lan driver software to set the ieee address by writing to the mac?s addrh and addrl registers. the host can initiate a reload of the mac address from t he eeprom by issuing the reload command via the e2p command (e2p_cmd) register. if the first byte read from the eeprom is not a5h, it is assumed that the eeprom is not pres ent, or not programmed, and the mac address reload will fail. the ?mac address loaded? bit indicates a successful reload of the mac address. 3.8.2 eeprom host operations after the eeprom controller has finished reading (or attempting to read) the mac after power-on, hard reset or soft reset, the host is free to perform other eeprom op erations. eeprom operations are performed using the e2p_cmd and e2 p data (e2p_data) registers. section 5.3.23, "e2p_cmd ? eeprom command register," on page 98 provides an explanation of the supported eeprom operations. if the eeprom operation is the ?write location? (write) or ?write all? (wral) commands, the host must first write the desired data into the e2p_data register. the host must then issue the write or wral command using the e2p_cmd register by setting the epc_cmd field appropriately. if the operation is a write, the epc_addr field in e2p_cmd must also be set to the desired location. the command is executed when the host sets the epc_ bsy bit high. the completi on of the operation is indicated when the epc_bsy bit is cleared. if the eeprom operation is the ?read location? (read) operation, the host must issue the read command using the e2p_cmd with the epc_addr se t to the desired location. the command is executed when the host sets the epc_bsy bit high. the completion of the operation is indicated when the epc_bsy bit is cleared, at which time t he data from the eeprom may be read from the e2p_data register. other eeprom operations are per formed by writing the appropr iate command to the epc_cmd register. the command is executed when the host se ts the epc_bsy bit high. the completion of the operation is indicated when the epc_bsy bit is clear ed. in all cases the host must wait for epc_bsy to clear before modifying the e2p_cmd register. note: the eeprom device powers-up in the erase/write disabled state. to modify the contents of the eeprom the host must fi rst issue the ewen command. if an operation is attempted, and an eeprom de vice does not respond within 30ms, the LAN9215 will timeout, and the epc timeout bit (epc_to) in the e2p_cmd register will be set. figure 3.2, "eeprom a ccess flow diagram" illustrates the host acce sses required to perform an eeprom read or write operation.
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet revision 2.9 (03-01-12) 36 smsc LAN9215 datasheet the host can disable the eeprom interface through the gpio_cfg re gister. when the interface is disabled, the eedio and eclk signals can be used as general-purpose outputs, or they may be used to monitor internal mii signals. 3.8.2.1 supported eeprom operations the eeprom controller supports the following eeprom operations under host control via the e2p_cmd register. the operations are commonly supported by ?93c46? eeprom devices. a description and functional timing diagram is provided below for each operation. please refer to the e2p_cmd register description in section 5.3.23, "e2p_cmd ? eeprom command register," on page 98 for e2p_cmd field settings for each command. figure 3.2 eeprom ac cess flow diagram id le write data register write command register read command register busy bit = 0 id le write command regis ter read command regis ter read data regis ter busy bit = 0 eeprom write eeprom read
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet smsc LAN9215 37 revision 2.9 (03-01-12) datasheet erase (erase location): if erase/write operations are enabled in the eeprom, this command will erase the location selected by the epc address fi eld (epc_addr). the epc_to bit is set if the eeprom does not respond within 30ms. figure 3.3 eeprom erase cycle eral (erase all): if erase/write operations are enabled in the eeprom, this command will initiate a bulk erase of the entire eeprom .the epc_to bit is set if the eeprom does not respond within 30ms. figure 3.4 eeprom eral cycle 1 eeclk eedio (input) eedio (output) eecs 11 a6 a0 t csl 0 eeclk eedio (input) eedio (output) eecs 10 10 t csl
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet revision 2.9 (03-01-12) 38 smsc LAN9215 datasheet ewds (erase/write disable): after issued, the eeprom will ignore erase and write commands. to re-enable erase/write operatio ns issue the ewen command. figure 3.5 eeprom ewds cycle ewen (erase/write enable): enables the eeprom for erase and write operat ions. the eeprom will allow erase and write operations until the ?era se/write disable? command is sent, or until power is cycled. note: the eeprom device will power-up in the erase/ write-disabled state. any erase or write operations will fail until an eras e/write enable command is issued. figure 3.6 eeprom ewen cycle 0 eeclk eedio (input) eedio (output) eecs 10 00 t csl 0 eeclk eedio (input) eedio (output) eecs 10 11 t csl
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet smsc LAN9215 39 revision 2.9 (03-01-12) datasheet read (read location): this command will cause a read of the eeprom location pointed to by epc address (epc_addr). the result of the read is available in the e2p_data register. figure 3.7 eeprom read cycle write (write location): if erase/write operatio ns are enabled in the eeprom, this command will cause the contents of the e2p_data register to be writ ten to the eeprom loca tion selected by the epc address field (epc_addr). the epc_to bit is set if the eeprom does not respond within 30ms. figure 3.8 eeprom write cycle wral (write all): if erase/write operations are enabled in the eeprom, this command will cause the contents of the e2p_data register to be written to every eepr om memory location. the epc_to bit is set if the eeprom does not respond within 30ms. figure 3.9 eeprom wral cycle 1 10 a6 eecs eeclk eedio (output) a0 d7 d0 eedio (input) t csl 0 eeclk eedio (input) eedio (output) eecs 11 a6 a0 d7 d0 t csl 0 eeclk eedio (input) eedio (output) eecs 1 d7 d0 0 01 t csl
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet revision 2.9 (03-01-12) 40 smsc LAN9215 datasheet table 3.8, "required eeclk cycles" , shown below, shows the number of eeclk cycles required for each eeprom operation. 3.8.2.2 mac address reload the mac address can be reloaded from the eeprom via a host command to the e2p_cmd register. if a value of 0xa5h is not found in the first address of the eeprom, the eeprom is assumed to be un-programmed and mac address reload operation will fail. the ?mac address loaded? bit indicates a successful load of the mac address. the epc_load bit is set after a successful reload of the mac address. 3.8.2.3 eeprom command and data registers refer to section 5.3.23, "e2p_cmd ? eeprom command register," on page 98 and section 5.3.24, "e2p_data ? eeprom data register," on page 100 for a detailed description of these registers. supported eeprom operat ions are described in these sections. 3.8.2.4 eeprom timing refer to section 6.9, "eeprom timing," on page 132 for detailed eeprom ti ming specifications. 3.9 power management the LAN9215 supports power-down modes to allow app lications to minimize power consumption. the following sections describe these modes. 3.9.1 system description power is reduced to various modules by disabling the clocks as outlined in table 3.9, ?power management states,? on page 42. all configuration data is saved when in either of the two low power states. register contents are not affected unless s pecifically indicated in the register description. 3.9.2 functional description there is one normal operating power state, d0 and there are two power saving states: d1, and d2. upon entry into either of the two power saving st ates, only the pmt_ctrl register is accessible for read operations. in either of the power saving st ates the ready bit in the pmt_ctrl register will be cleared. reads of any other addresses are forbidden until the ready bit is set. all writes, with the exception of the wakeup write to byte_test, are also forbidden until the ready bit is set. only when in the d0 (normal) state, when the ready bit is set, can the rest of the device be accessed. table 3.8 required eeclk cycles operation required eeclk cycles erase 10 eral 10 ewds 10 ewen 10 read 18 write 18 wral 18
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet smsc LAN9215 41 revision 2.9 (03-01-12) datasheet note 3.4 the LAN9215 must always be read at least on ce after power-up, rese t, or upon return from a power-saving state, otherwise write operations will not function. in system configurations where the pme signal is shared am ongst multiple devices, the wups field within the pmt_ctrl register can be read to de termine which LAN9215 device is driving the pme signal. when the LAN9215 is in a power saving state (d1 or d2), a write cycle to the byte_test register will return the LAN9215 to the d0 state. table 7.2, ?power consumption device and system components,? on page 135 and table 7.2, ?power consumption device and system components,? on page 135 , shows the power consumption values for each power state. note 3.5 when the LAN9215 is in a power saving st ate, a write of any data to the byte_test register will wake-up the device. do not perform writes to other addrresses while the ready bit in the pmt_ctrl register is cleared. 3.9.2.1 d1 sleep power consumption is reduced in this state by disabling clocks to portions of the internal logic as shown in ta b l e 3 . 9 . in this mode the clock to the internal phy and portions of the mac are still operational. this state is enter ed when the host writes a '01' to the pm_mode bits in the power management (pmt_ctrl) register. the ready bit in pmt_ctrl is cleared when entering the d1 state. wake-up frame and magic packet dete ction are automatically enabled in the d1 state. if properly enabled via the wol_en and pme_en bits, the la n9215 will assert the pme hardware signal upon the detection of the wake-up frame or magic packet. the LAN9215 can also assert the host interrupt (irq) on detection of a wake-up frame or magic pa cket. upon detection, the wups field in pmt_ctrl will be set to a 10b. note 3.6 the pme interrupt status bit (pme_int) in t he int_sts register is set regardless of the setting of pme_en. note 3.7 wake-up frame and magic packet detection is automatically enabled when entering the d1 state. for wake-up fr ame detection, the wake-up frame f ilter must be programmed before entering the d1 state (see section 3.5, "wake-up frame detection," on page 30 ). if used, the host interrupt and pme signal must be enabled prior to entering the d1 state. a write to the byte_test register, regardless of whether a wake-up frame or magic packet was detected, will return LAN9215 to the d0 state and will reset the pm_mode field to the d0 state. as noted above, the host is required to check the ready bit and verify that it is set before attempting any other reads or writes of the device. note 3.8 the host must only perform read accesses prior to the ready bit being set. once the ready bit is set, the LAN9215 is ready to resume normal operation. at this time the wups field can be cleared. 3.9.2.2 d2 sleep in this state, as shown in ta b l e 3 . 9 , all clocks to the mac and host bus are disabled and the phy is placed in a reduced power state. to enter this stat e, the edpwrdown bit in register 17 of the phy (mode control/status register) must be set. this places the phy in the energy detect mode. the pm_mode bits in the pmt_ctrl register must t hen be set to 10b. upon setting the pm_mode bits, the LAN9215 will enter the d2 sleep state. the read y bit in pmt_ctrl is cleared when entering the d2 state. note 3.9 if carrier is present when this state is entered detection will occur immediately. if properly enabled via the ed_en and pme_en bits, the LAN9215 will assert the pme hardware signal upon detection of a valid carrier. upon detection, the wups field in pmt_ctrl will be set to a 01b.
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet revision 2.9 (03-01-12) 42 smsc LAN9215 datasheet note 3.10 the pme interrupt status bit on the int_sts register (pme_int) is set regardless of the setting of pme_en. a write to the byte_test register, regardless of whether a carrier was detected, will return the LAN9215 to the d0 state and will reset the pm_mode field to the d0 state. as noted above, the host is required to check the ready bit and verify that it is set before attempting any other reads or writes of the device. before the LAN9215 is fully awake from this state the edpwrdown bit in register 17 of the phy must be cleared in order to wake the phy. do not attempt to clear the edpwrdown bit until the ready bit is set. after clearing the ed pwrdown bit the LAN9215 is ready to resume normal operation. at this time the wups field can be cleared. table 3.9 power management states device block d0 (normal operation) d1 (wol) d2 (energy detect) phy full on full on energy detect power-down mac power management full on rx power mgmt. block on off mac and host interface full on off off internal clock full on full on off key clock on block disabled ? clock on full off
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet smsc LAN9215 43 revision 2.9 (03-01-12) datasheet 3.9.2.3 power manageme nt event indicators figure 3.10 is a simplified block diagram of the logic that controls the external pme, and internal pme_interrupt signals. the pme_inter rupt signal is used to set the pme_int status bit in the int_sts register, which, if enabled, will generate a host interr upt upon detection of a power management event. the pme_int status bit in int_sts will remain set un til the internal pme_interrupt signal is cleared by clearing the wups bits, or by clearing the corre sponding wol_en or ed_en bit. after clearing the internal pme_interrupt signal, the pme_int status bit may be cleared by writing a ?1? to this bit in the int_sts register. it should be noted that the lan9 215 can generate a host interrupt regardless of the state of the pme_en bit, or the external pme signal. the external pme signal can be setup for pulsed, or static operation. when the pme_ind bit in the pmt_ctrl register is set to a ?1?, the external pme signal will be driven active for 50ms upon detection of a wake-up event. when the pme_ind bit is cleared, the pme signal will be driven continuously upon detection of a wake-up event. th e pme signal is deactivated by clearing the wups bits, or by clearing the corresponding wol_en or ed _en bit. the pme signal can also be deactivated by clearing the pme_en bit. figure 3.10 pme and pme_int signal generation 3.9.3 internal phy power-down modes there are 2 power-down modes for the internal phy: 3.9.3.1 general power-down this power-down is controlled by r egister 0, bit 11. in this mode the internal phy, except the management interface, is powered-down and stays in that condition as long as phy register bit 0.11 is high. when bit 0.11 is cleared, the phy powers up and is automatically reset. please refer to section 5.5.1, "basic control register," on page 113 for additional information on this register. pme ed_en wol_en 50ms pme_en pme_ind pme_pol pme_type logic wuen mpen phy_int wups wups wufr mpr denotes a level-triggered "sticky" status bit pme_int_en pme_int irq_en irq other system interrupts
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet revision 2.9 (03-01-12) 44 smsc LAN9215 datasheet 3.9.3.2 energy detect power-down this power-down mode is activated by setting the phy register bit 17.13 to 1. please refer to section 5.5.8, "mode control/status," on page 117 for additional information on this register. in this mode when no energy is present on the line, the phy is powered down, with the e xception of the management interface, the squelch circuit and the energyon logic. the energyon logic is used to detect the presence of valid energy from 100base- tx, 10base-t, or auto-negotiation signals in this mode, when the energyon signal is low, the phy is powered-down, and nothing is transmitted. when energy is received - link pulses or packets - the energyon signal goes high, and the phy powers-up. it automatically resets itself into the state it had prior to power-down, and asserts the int7.1 bit of the register defined in section 5.5.11, "interrupt source flag," on page 120 . if the energyon interrupt is enabled, this event will cause an interrupt to the host. the first and possibly the second packet to activate energyon may be lo st. when 17.13 is low, energy detect power-down is disabled. 3.10 detailed reset description the LAN9215 has five reset sources: ? power-on reset (por) ? hardware reset input pin (nreset) ? soft reset (srst) ? phy soft reset via pmt_ctrl bit 10 (phy_rst) ? phy soft reset via phy basic co ntrol register (phy reg 0.15) table 3.10 shows the effect of the various rese t sources on the LAN9215's circuitry. note 3.11 after any phy reset, the application must wait until the ?link status? bit in the phy?s ?basic status register? (phy reg. 1.2) is set bef ore attempting to transmit or receive data. note 3.12 after a por, nreset or srst, the LAN9215 will automatically check for the presence of an external eeprom. after any of these rese ts the application must verify that the epc busy bit (e2p_cmd, bit 31) is cleared bef ore attempting to access the eeprom, or change the function of the gpo/gpio sign als, or before modify ing the addrh or addrl registers in the mac. note 3.13 hbi - ?host bus interface?, nasr - not affected by software reset. table 3.10 reset sources and affected circuitry reset source pll hbi note 3.13 nasr registers note 3.13 mil mac phy note 3.11 eeprom mac addr. reload note 3.12 config. straps latched por xx x x x x x x nreset xx x x x x x x srst xxx x phy_rst x phy reg 0.15 x
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet smsc LAN9215 45 revision 2.9 (03-01-12) datasheet 3.10.1 power-on reset (por) a power-on reset occurs whenever power is initially applied to the LAN9215, or if power is removed and reapplied to the LAN9215. a timer within the LAN9215 will assert the internal reset for approximately 22ms. the ready bit in the pmt_ctrl register can be read from the host interface and will read back a ?0? until the por is complete . upon completion of the por, the ready bit in pmt_ctrl is set high, and the LAN9215 c an be configured via its control registers. application note: under normal conditions, the ready bit in pmt_ ctrl will be set (high -?1?) after an internal reset (22ms). if the software driver polls this bit and it is not set within 100ms, then an error condition occurred. 3.10.2 hardware reset input (nreset) a hardware reset will occur when the nreset input signal is driven low. the ready bit in the pmt_ctrl register can be read fr om the host interface, and will read back a ?0? until the hardware reset is complete. upon completion of the hardware reset, the ready bit in pmt_ctrl is set high. after the ?ready? bit is set, the LAN9215 can be configured via its cont rol registers. the nreset signal is pulled-high internally by the LAN9215 and can be left unconnected if unused. if used, nreset must be driven low for a minimum period as defined in section 6.8, "reset timing," on page 131 . application note: under normal conditions, the ready bit in pmt_ctrl will be set (high -?1?) immediately. if the software driver polls this bit and it is not set within 100ms, then an error condition occurred. 3.10.3 resume reset timing after issuing a write to the byte_test register to wake the LAN9215 from a power-down state, the ready bit in pmt_ctrl will assert (set high) within 2ms. application note: under normal conditions, the ready bit in pm t_ctrl will be set (high -?1?) within 2 ms. if the software driver polls this bit and it is not set within 100ms, then an error condition occurred. 3.10.4 soft reset (srst) soft reset is initiated by writing a ?1? to bit 0 of the hw_cfg register (srst). this self-clearing bit will return to ?0? after approximately 2 s, at which time the soft reset is complete. soft reset does not clear control register bits marked as nasr. application note: under normal conditions, the ready bit in pmt_ctrl will be set (high -?1?) immediately, (within 2 s). if the software driver polls this bit and it is not set within 100ms, then an error condition occurred. 3.10.5 phy reset timing the following sections specify the operation and time required for the internal phy to become operational after various resets or when returning from the reduced power state. 3.10.5.1 phy soft reset via pmt_ctrl bit 10 (phy_rst) the phy soft reset is initiated by writing a ?1? to bit 10 of the pmt_ctrl register (phy_rst). this self-clearing bit will return to ?0? after approximately 100 s, at which time the phy reset is complete.
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet revision 2.9 (03-01-12) 46 smsc LAN9215 datasheet 3.10.5.2 phy soft reset via phy basic control register (phy reg. 0.15) the phy reg. 0.15 soft reset is in itiated by writing a ?1? to bit 15 of the phy?s basic control register. this self-clearing bit will return to ?0? at which time the phy reset is complete. 3.11 mii interface - external mii switching there are two mechanisms that are used to switch between the internal phy and the external mii port. ? a lan driver or other software controlled mech anism is used to control the phy_clk_sel[1:0] bits described in section 5.3.9, "hw_cfg?hardwa re configuration register" that provides glitch- free mii clock switching. this mechanism allows the host processor to disable (gate) the rx_clk and tx_clk clocks from both the internal phy an d the external mii port, and switch the clock sources once they have stopped. after switching the clocks, the LAN9215 transmitter and receiver can be re-enabled. ? a simple multiplexor that , with the exception of the smi bus and the mii clocks, will switch the remaining mii signals. this multiplexor is controlled by the ext_phy_en bit described in section 5.3.9, "hw_cfg?hardware configuration register" 3.11.1 smi switching the serial management interface (smi) port can be switched between the internal phy and external mii ports based on the settings of the smi_sel bit described in section 5.3.9, "hw_cfg?hardware configuration register" . the smi port can be switched independent of the setting of the other mii signals. application note: the user is cautioned to not s witch the smi port while an smi transaction is in progress. 3.11.2 mii clock switching the LAN9215 supports dynamic switching between th e integrated internal phy and the external mii port which can connect to an external mii compatible ethernet phy device. the remaining mii signals, with the exception of the smi port, are swit ched using a simple multiplexor controlled by the ext_phy_sel bit described in section 5.3.9, "hw_cfg?hardware configuration register" . it is required that the mii clocks be disabl ed before the other mii signals are switched. the steps outlined in the flow diagram in figure 3.11, "mii switching procedure" , detail the required procedure for switching the mii po rt, including the mii clocks. these steps must be followed in order to guarantee clean switch ing of the mii ports. using the smi interface, both the internal phy, and the external phy must be placed in a stable state. for each device generating a tx_clk or rx_clk, this clock must be stable and glitch-free before the switch can be made. if either device is not gener ating a tx_clk or rx_clk, this clock must remain off until the switch is complete. in either case t he tx_clk and rx_clk must be stable and glitch-free for the device that will be selected after the s witch. the following must be done prior to a switch: ? the LAN9215 transmitter must be halted. ? the halting of the LAN9215 transmitter must be complete ? the LAN9215 receiver must be halted. ? the halting of the LAN9215 receiver must be complete. ? the phy_clk_sel field must be set to 10b. this action will disabl e the mii clocks to the LAN9215 internal logic for both the internal phy, and the external mii interface. ? the host must wait a period of time not less than 5 cycles of the slowest operating clock before executing the next step in this procedure.
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet smsc LAN9215 47 revision 2.9 (03-01-12) datasheet application note: for example, if the internal phy was operating in 10mbs mode, and the external phy was operating at 100mbs mode, the internal phy?s tx_clk and rx_clk period is the longest, and will determine the required wait-time. in this case the tx_clk and rx_clk period for the internal phy is 400ns, therefore the host must wait 2us (5*400ns) before proceeding. if the clocks of the device being deselected by the switch are not running, they are not considered in this calculation. ? set ext_phy_sel described in section 5.3.9, "hw_cfg?hardwa re configuration register" to the desired mii port. this step switches the rxd[3:0], rx_dv, rx_er, txd[3:0], tx_en, crs and col signals to the desired port. ? set phy_clk_sel described in section 5.3.9, "hw_cfg?hardwa re configuration register" to the desired port. this must be the same port that is selected by ext_phy_sel. ? the host must wait a period of time of not less than 5 cycles of the slowest, newly enabled clock before executing the next step in this procedure. ? enable the LAN9215 transmitter. ? enable the LAN9215 receiver. the process is complete. the LAN9215 is now o perational using the newly selected mii device. the above procedure must be repeated each time the mii port is switched. the procedure is identical when switching from internal phy to external mii, or vice-versa.
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet revision 2.9 (03-01-12) 48 smsc LAN9215 datasheet figure 3.11 mii switching procedure tx stopped? halt transmitter halt receiver rx stopped? set phy_clk_sel to 10b clocks halted? set ext_phy_sel to desired mii port set phy_clk_sel to desired mii port enable rx enable tx 1 2 3 4 5 6 8 9 11 12 complete yes no yes no yes no using smi, set internal phy and external phy to a stable state 7 13 10 clocks running yes no
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet smsc LAN9215 49 revision 2.9 (03-01-12) datasheet 3.12 tx data path operation data is queued for transmission by writing it into the tx data fifo. each packet to be transmitted may be divided among multiple buffers. each buffer st arts with a two dword tx command (tx command ?a? and tx command ?b?). the tx command instru cts the LAN9215 on the handling of the associated buffer. packet boundaries are delineated usin g control bits within the tx command. the host provides a 16-bit packet tag field in the tx command. the packet tag value is appended to the corresponding tx status dword. all packet t ag fields must have the same value for all buffers in a given packet. if tags differ between buffers in the same packet the txe error will be asserted. any value may be chosen for a packet tag as long as all tags in the same packet are identical. packet tags also provide a method of synchronization between transmitted packets and their associated status. software can use unique packet tags to assist with validating matching status completions. note 3.14 the use of packet tags is not required by the hardware. this is a software lan driver only application example for use of this field. a packet length field in the tx command specifies th e number of bytes in the associated packet. all packet length fields must have the same value for all buffers in a given packet. hardware compares the packet length field and the actual amount of data received by the ethernet controller. if the actual packet length count does not match the packet length field as defined in the tx command, the transmitter error (txe) flag is asserted. the LAN9215 can be programmed to start payloa d transmission of a buffer on a byte boundary by setting the ?data start offset? field in the tx command. the ?data start offset? field points to the actual start of the payload data within the first 8 dwords of the buffer. data before the ?data start offset? pointer will be ignored. when a packet is split into multiple buffers, each successive buffer may begin on any arbitrary byte. the LAN9215 can be programmed to strip padding from the end of a transmit packet in the event that the end of the packet does not align with the host burst boundary. this feature is necessary when the LAN9215 is operating in a system t hat always performs multi-word burst s. in such cases the LAN9215 must guarantee that it can accept data in multiples of the burst length regardless of the actual packet length. when configured to do so, the LAN9215 will accept extra data at the end of the packet and will remove the extra padding befor e transmitting the packet. the LAN9215 automatically removes data up to the boundary specified in the buffer end alignment field specified in each tx command. the host can instruct the LAN9215 to issue an interr upt when the buffer has been fully loaded into the tx fifo contained in the lan92 15 and transmitted. this feature is enabled through the tx command ?interrupt on completion? field. upon completion of transmission, irrespective of success or failure, the status of the transmission is written to the tx status fifo. tx status is available to the host and may be read using pio operations. an interrupt can be optionally enabled by the host to indicate the availability of a programmable number tx status dwords. before writing the tx command and payload data to the tx fifo, the host mu st check the available tx fifo space by performing a pi o read of the tx_fifo_inf register. the host must ensure that it does not overfill the tx fifo or the tx error (txe) flag will be asserted. the host proceeds to write the tx command by first writing tx command ?a?, then tx command ?b?. after writing the command, the host can then move the payload data into the tx fifo. tx status dword?s are stored in the tx status fifo to be read by the host at a later time upon completion of the data transmission onto the wire.
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet revision 2.9 (03-01-12) 50 smsc LAN9215 datasheet 3.12.1 tx buffer format tx buffers exist in the host?s memory in a given fo rmat. the host writes a tx command word into the tx data buffer before moving the ethernet pack et data. the tx command a and command b are 32- bit values that are used by the LAN9215 in the handling and processing of the associated ethernet packet data buffer. buffer alignment, segmentati on and other packet processing parameters are included in the command structure. the follo wing diagram illustrates the buffer format. figure 3.12 simplified host tx flow diagram idle check available fifo space init write tx command write buffer last buffer in packet not last buffer write start padding (optional) read tx status (optional) tx status available
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet smsc LAN9215 51 revision 2.9 (03-01-12) datasheet figure 3.13, "tx buffer format" , shows the tx buffer as it is wr itten into the LAN9215. it should be noted that not all of the data shown in this diagram is actually stored in the tx data fifo. this must be taken into account when calculating the actu al tx data fifo usage. please refer to section 3.12.5, "calculating actual tx data fifo usage," on page 55 for a detailed explanation on calculating the actual tx data fifo usage. note 3.15 the LAN9215 host bus interface supports 16-bit bus transfers; internally, all data paths are 32-bits wide. figure 3.13 describes the host write orderi ng for pairs of atomic 16-bit transactions. 3.12.2 tx command format the tx command instructs the tx fifo controlle r on handling the subsequent buffer. the command precedes the data to be transmitted. the tx command is divided into two, 32-bit words; tx command ?a? and tx command ?b?. there is a 16-bit packet tag in the tx command ?b? command word. packet tags may, if host software desires, be unique for each packet (i.e., an incrementing count). the value of the tag will be returned in the rx status word for the associated packet. the packet tag can be used by host software to uniquely identify each status word as it is returned to the host. figure 3.13 tx buffer format tx command 'a' offset + data dword0 . . . . . last data & pad 0 31 1st 2nd 3rd last host write order optional pad dword0 . . . optional pad dwordn tx command 'b' optional offset dword0 . . . optional offset dwordn
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet revision 2.9 (03-01-12) 52 smsc LAN9215 datasheet both tx command ?a? and tx command ?b? are r equired for each buffer in a given packet. tx command ?b? must be identical for every buffer in a given packet. if the tx command ?b? words do not match, the ethernet controller will as sert the transmitter error (txe) flag. tx command ?a? table 3.11 tx command 'a' format bits description 31 interrupt on completion. when set, the txdone flag will be asserted when the current buffer has been fully loaded into the tx fifo. this flag may be optionally mapped to a host interrupt. 30:26 reserved. these bits are reserved. always write zeros to this field to guarantee future compatibility. 25:24 buffer end alignment. this field specifies the alignment that must be maintained on the last data transfer of a buffer. the host will add extra dwo rds of data up to the alignment specified in the table below. the LAN9215 will remove the extra dwords. this mechanism can be used to maintain cache line alignment on host processors. 23:21 reserved. these bits are reserved. always write zeros to this field to guarantee future compatibility 20:16 data start offset (bytes). this field specifies the offs et of the first byte of tx data. the offset value can be anywhere from 0 bytes to 31 a byte offset. 15:14 reserved. these bits are reserved. always write zeros to this field to guarantee future compatibility 13 first segment (fs). when set, this bit indicates that the asso ciated buffer is the first segment of the packet. 12 last segment. when set, this bit indicates that the asso ciated buffer is the last segment of the packet 11 reserved. these bits are reserved. always write zeros to this field to guarantee future compatibility. 10:0 buffer size (bytes). this field indicates the number of bytes contained in the buffer following this command. this value, along with the buffer end alignment field, is read and checked by the LAN9215 and used to determine how many extra dword?s were added to the end of the buffer. a running count is also maintained in the LAN9215 of the cumulative buffer sizes for a given packet. this cumulative value is compared against the packet length field in the tx command ?b? word and if they do not correlate, the txe flag is set. note: the buffer size specified does not include the buffer end alignment padding or data start offset added to a buffer. [25] [24] end alignment 0 0 4-byte alignment 0 1 16-byte alignment 1 0 32-byte alignment 11 reserved
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet smsc LAN9215 53 revision 2.9 (03-01-12) datasheet tx command ?b? 3.12.3 tx data format the tx data section begins at the third dword in the tx buffer (after tx command ?a? and tx command ?b?). the location of the first byte of vali d buffer data to be transmitted is specified in the ?data start offset? field of the tx command ?a? word. table 3.13, "tx data start offset" , shows the correlation between the setting of the lsb?s in the ?data start offset? field and the byte location of the first valid data byte. additionally, transmit buffer data can be offset by up to 7 additional dwords as indicated by the upper three msb?s (5:2) in the ?data start offset? field. tx data is contiguous until the end of the buffer. the buffer may end on a byte boundary. unused bytes at the end of the packet will not be sent to the mil for transmission. the buffer end alignment field in tx command ?a? specifies the alignment t hat must be maintained for the associated buffer. end alignment may be specified as 4-, 16-, or 32-byte. the host processor is responsible for adding the additional data to the end of the buffer. the hardware will automatically remove this extra data. 3.12.3.1 tx buffer fragmentation rules transmit buffers must adhere to the following rules: ? each buffer can start and end on any arbitrary byte alignment ? the first buffer of any transmit packet can be any length ? middle buffers (i.e., those with first segment = la st segment = 0) must be greater than, or equal to 4 bytes in length ? the final buffer of any transmit packet can be any length table 3.12 tx command 'b' format bits description 31:16 packet tag. the host should write a unique packet identifier to this field. this identifier is added to the corresponding tx status word and can be used by the host to correlate tx status words with their corresponding packets. note: the use of packet tags is not required by the hardware. this field can be used by the lan software driver for any application. packet tags is one application example. 15:14 reserved. these bits are reserved. always write zeros to this field to guarantee future compatibility. 13 add crc disable. when set, the automatic addi tion of the crc is disabled. 12 disable ethernet frame padding. when set, this bit prevents the automatic addition of padding to an ethernet frame of less than 64 bytes. the crc field is also added despite the state of the add crc disable field. 11 reserved. these bits are reserved. always write zeros to this field to guarantee future compatibility. 10:0 packet length (bytes). this field indicates the total number of bytes in the current packet. this length does not include the offset or padding. if the packet length field does not match the actual number of bytes in the packet the transmitter error (txe) flag will be set. table 3.13 tx data start offset data start offset [1:0]: 11 10 01 00 first tx data byte: d[31:24] d[23:16] d[15:8] d[7:0]
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet revision 2.9 (03-01-12) 54 smsc LAN9215 datasheet the mil operates in store-and-forward mode and has specific rules with respect to fragmented packets. the total space consumed in the tx fifo (mil) must be limited to no more than 2kb - 3 dwords (2,036 bytes total). any transmit packet that is so highly fragmented that it takes more space than this must be un-fragmented (by copying to a driver-supplied buffer) before the transmit packet can be sent to the LAN9215. one approach to determine whether a packet is too fragmented is to calculate the actual amount of space that it will consume, and check it against 2, 036 bytes. another approach is to check the number of buffers against a worst-case limit of 86 (see explanation below). 3.12.3.2 calculating worst-ca se tx fifo (mil) usage the actual space consumed by a buffer in the mil tx fifo consists only of any partial dword offsets in the first/last dword of the buffer, plus all of the whole dwords in between. any whole dword offsets and/or alignments are stri pped off before the buffer is loaded into the tx data fifo, and tx command words are stripped off before the buffer is written to the mil tx fifo, so none of those dwords count as space consumed. the worst-case overhead for a tx buffer is 6 bytes, which assumes that it started on the high byte of a dword and ended on the low byte of a dword. a tx packet consisting of 86 such fragments would have an overhead of 516 bytes (6 * 86) which, when added to a 1514-byte max-size transmit packet (15 16 bytes, rounded up to the next whole dword), would give a total space consumption of 2,032 bytes, leaving 4 bytes to spare; this is the basis for the "86 fragment" rule mentioned above. 3.12.4 tx status format tx status is passed to the host cpu through a sepa rate fifo mechanism. a status word is returned for each packet transmitted. data transmission is suspended if the tx status fifo becomes full. data transmission will resume when the host reads the tx status and there is ro om in the fifo for more ?tx status? data. the host can optionally choose to not read the tx st atus. the host can optionally ignore the tx status by setting the ?tx status discard allow overrun en able? (txsao) bit in the tx configuration register (tx_cfg). if this option is chosen tx status will not be written to the fifo. setting this bit high allows the transmitter to continue operation with a full tx status fifo. in this mode the status information is still available in the tx status fifo, and tx status interrupts still function. in the case of an overrun, the txsused counter will stay at zero and no further tx status will be written to the tx status fifo until the host frees space by reading tx status. if txsao is enabled, a txe error will not be generated if the tx status fifo overruns. in this mode the host is responsible for re-synchronizing tx status in the case of an overrun. bits description 31:16 packet tag. unique identifier written by the host into the packet tag field of the tx command ?b? word. this field can be used by the host to correlate tx status words with the associated tx packets. 15 error status (es). when set, this bit indicates that the ethernet controller has reported an error. this bit is the logical or of bits 11, 10 , 9, 8, 2, 1 in this status word. 14:12 reserved. these bits are reserved. always write zeros to this field to guarantee future compatibility. 11 loss of carrier. when set, this bit indicates the loss of carrier during transmission. 10 no carrier. when set, this bit indicates that the carrier signal from the transceiver was not present during transmission. note: during 10/100 mbps full-duplex transmission, the value of this bit is invalid and should be ignored. 9 late collision. when set, indicates that the packet transmission was aborted after the collision window of 64 bytes.
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet smsc LAN9215 55 revision 2.9 (03-01-12) datasheet 3.12.5 calculating actual tx data fifo usage the following rules are used to calculate the act ual tx data fifo space consumed by a tx packet: ? tx command 'a' is stored in the tx data fifo for every tx buffer. ? tx command 'b' is written into the tx data fifo when the first segment (fs) bit is set in tx command 'a.' ? any dword-long data added as part of the ?data start offset? is removed from each buffer before the data is written to the tx data fifo. any dat a that is less than 1 dword is passed to the tx data fifo. ? payload from each buffer within a packe t is written into the tx data fifo. ? any dword-long data added as part of the end p adding is removed from each buffer before the data is written to the tx data fifo. any end padd ing that is less than 1 dword is passed to the tx data fifo. 3.12.6 transmit examples 3.12.6.1 tx example 1 in this example a single, 111-byte ethernet packet will be transmitted. this packet is divided into three buffers. the three buffers are as follows: buffer 0: ? 7-byte ?data start offset? ? 79-bytes of payload data ? 16-byte ?buffer end alignment? buffer 1: ? 0-byte ?data start offset? ? 15-bytes of payload data ? 16-byte ?buffer end alignment? buffer 2: ? 10-byte ?data start offset? ? 17-bytes of payload data ? 16-byte ?buffer end alignment? 8 excessive collisions. when set, this bit indicates that th e transmission was aborted after 16 collisions while attempting to transmit the current packet. 7 reserved. this bit is reserved. always write zeros to this field to guarantee future compatibility. 6:3 collision count. this counter indicates the number of colli sions that occurred before the packet was transmitted. it is not valid when excessive collisions (bit 8) is also set. 2 excessive deferral. if the deferred bit is set in the contro l register, the setting of the excessive deferral bit indicates that the transmission has ended because of a deferral of over 24288 bit times during transmission. 1 reserved. this bit is reserved. always write zero to this bit to guarantee future compatibility. 0 deferred. when set, this bit indicates that the current packet transmission was deferred. bits description
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet revision 2.9 (03-01-12) 56 smsc LAN9215 datasheet figure 3.14, "tx example 1" illustrates the tx command structure for this example, and also shows how data is passed to the tx data fifo. note 3.16 the LAN9215 host bus interface supports 16-bit bus transfers; internally, all data paths are 32-bits wide. figure 3.14 and figure 3.15 describe the host writ e ordering for pairs of atomic 16-bit transactions. figure 3.14 tx example 1 tx command 'a' 0 31 tx command 'b' pad dword 1 7-byte data start offset 10-byte end padding 79-byte payload buffer end alignment = 1 data start offset = 7 first segment = 1 last segment = 0 buf f er size = 79 packet length = 111 tx command 'a' 0 31 tx command 'b' 10-byte end offset padding 15-byte payload buffer end alignment = 1 data start offset = 0 first segment = 0 last segment = 0 buf f er size = 15 packet length = 111 tx command 'a' 0 31 tx command 'b' buffer end alignment = 1 data start of fset = 10 first segment = 0 last segment = 1 buf f er size = 17 packet length = 111 10-byte data start offset tx command 'a' tx command 'b' tx command 'a' tx command 'b' tx command 'a' tx command 'b' note: extra bytes betw een buff ers are not transmitted data written to the ethernet controller data passed to the tx data fifo 5-byte end padding 17-byte payload data tx command 'a' tx command 'b' tx command 'a' tx command 'a' 1b 79-byte payload 15-byte payload 17-byte payload
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet smsc LAN9215 57 revision 2.9 (03-01-12) datasheet 3.12.6.2 tx example 2 in this example, a single 183-byte ethernet packet will be transmitted. this packet is in a single buffer as follows: ? 2-byte ?data start offset? ? 183-bytes of payload data ? 4-byte ?buffer end alignment? figure 3.15, "tx example 2" illustrates the tx command structure for this example, and also shows how data is passed to the tx data fifo. note that the packet resides in a single tx buffer, therefore both the fs and ls bits are set in tx command ?a?. figure 3.15 tx example 2 tx command 'a' 0 31 tx command 'b' data written to the ethernet controller tx command 'b' 183-byte payload data data start offset = 6 first segment = 1 last segment = 1 buffer size =183 packet length = 183 tx command 'a' tx command 'b' data passed to the tx data fifo buffer end alignment = 0 3b end padding tx command 'a' 6-byte data start offset 183-byte payload data note: extra bytes between buffers are not transmitted
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet revision 2.9 (03-01-12) 58 smsc LAN9215 datasheet 3.12.7 transmitter errors if the transmitter error (txe) flag is asserted fo r any reason, the transmit ter will continue operation. tx error (txe) will be asserted under the following conditions: ? if the actual packet length count does not matc h the packet length field as defined in the tx command. ? both tx command ?a? and tx command ?b? are required for each buffer in a given packet. tx command ?b? must be identical for every buffer in a given packet. if the tx command ?b? words do not match, the ethernet controller will assert the transmitter error (txe) flag. ? host overrun of the tx data fifo. ? overrun of the tx status fi fo (unless t xsao is enabled) 3.12.8 stopping and starting the transmitter to halt the transmitter, the host mu st set the tx_stop bit in the tx _cfg register. the transmitter will finish sending the current frame (if there is a fr ame transmission in progress). when the transmitter has received the tx status for this frame, it will clear the tx_stop and tx_on bits, and will pulse the txstop_int. once stopped, the host can optionally clear the tx status and tx data fifos. the host must re-enable the transmitter by setting the tx_o n bit. if the there ar e frames pending in the tx data fifo (i.e., tx data fifo was not purged), the transmission will resume with this data. 3.13 rx data path operation when an ethernet packet is received , the mil first begins to transfer the rx data. this data is loaded into the rx data fifo. the rx da ta fifo pointers are updated as data is written into the fifo. the last transfer from the mil is the rx status word. the LAN9215 implements a separate fifo for the rx status words. the total available rx data and status queued in the rx fifo can be read from the rx_fifo_inf register. the host may read any number of available rx status words before reading the rx data fifo. the host must use caution when reading the rx data and status. the host must never read more data than what is available in the fifos. if this is attempted an underrun condition will occur. if this error occurs, the ethernet controller will assert the receiv er error (rxe) interrupt. if an underrun condition occurs, a soft reset is required to regain host synchronization. a configurable beginning offset is supported in th e LAN9215. the rx data offset field in the rx_cfg register controls the num ber of bytes that the beginning of the rx data buffer is shifted. the host can set an offset from 0-31 bytes. the offset may be changed in between rx packets, but it must not be changed during an rx packet read. the LAN9215 can be programmed to add padding at the end of a receive packe t in the event that the end of the packet does not align with the host bu rst boundary. this featur e is necessary when the LAN9215 is operating in a system that always perf orms multi-dword bursts. in such cases the LAN9215 must guarantee that it can transfer data in multiples of the burst length regardless of the actual packet length. when configured to do so, the LAN9215 will add extra data at the end of the packet to allow the host to perform the necessary numbe r of reads so that the burst length is not cut short. once a packet has been padded by the h/w, it is the responsibility of the host to interrogate the packet length field in the rx status and determine how much padding to discard at the end of the packet. it is possible to read multiple packets out of t he rx data fifo in one c ontinuous stream. it should be noted that the programmed offset and padding will be added to each individual packet in the stream, since packet boundaries are maintained.
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet smsc LAN9215 59 revision 2.9 (03-01-12) datasheet 3.13.1 rx slave pio operation using pio mode, the host can eith er implement a polling or interru pt scheme to empty the received packet out of the rx data fifo. the host will remain in the idle state until it receives an indication (interrupt or polling) that data is available in the rx data fifo. the host will then read the rx status fifo to get the packet status, which will contain the packet length and any other status information. the host should perform the proper number of reads, as indicated by the packet length plus the start offset and the amount of optional padding added to t he end of the frame, from the rx data fifo. figure 3.16 host receive routine using interrupts figure 3.17 host receive routine with polling not last packet idle read rx status dword init read rx packet last packet rx interrupt read rx_fifo_ inf read rx status dword init read rx packet last packet not last packet valid status dword
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet revision 2.9 (03-01-12) 60 smsc LAN9215 datasheet 3.13.1.1 receive data fifo fast forward the rx data path implements an automatic data discard function. using the rx data fifo fast forward bit (rx_ffwd) in the rx_dp_ctrl register, the host can instruct the LAN9215 to skip the packet at the head of the rx data fifo. the rx da ta fifo pointers are aut omatically incremented to the beginning of the next rx packet. when performing a fast-forward, there must be at leas t 4 dwords of data in the rx data fifo for the packet being discarded. for less than 4 dwords do not use rx_ffwd. in this case data must be read from the rx data fifo and discard ed using standard pio read operations. after initiating a fast-forward operation, do not perfo rm any reads of the rx data fifo, rx status fifo, or the tx status fifo until the rx_ffwd bit is cleared. other resources can be accessed during this time (i.e., any registers and/or the tx data fifo). after the fast-forward operation has completed and the rx_ffwd bit has been cleared, a wait time re striction must be observed before reading the tx or rx status fifo?s, as specified in section 6.1.2, "special restrictio ns on back-to-back read cycles," on page 124 . also note that the rx_ffwd will only fast-f orward the rx data fi fo, not the rx status fifo. the receiver does not have to be sto pped to perform a fast-forward operation. 3.13.1.2 force receiver discard (receiver dump) in addition to the receive data fast forward feat ure, LAN9215 also implements a receiver "dump" feature. this feature allows the host processor to flush the entire contents of the rx data and rx status fifos. when activated, t he read and write pointers for the rx data and status fifos will be returned to their reset state. to perform a receiver dump, the LAN9215 receiver must be halted. once the receiver stop completion is confirmed, the rx _dump bit can be set in the rx_cfg register. the rx_dump bit is cleared when the dump is complete. for more information on stopping the receiver, please refer to section 3.13.4, "stopping and starting the receiver," on page 62 . for more information on the rx_dump bit, please refer to section 5.3.7, "rx_cfg?receiv e configuration register," on page 82 .
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet smsc LAN9215 61 revision 2.9 (03-01-12) datasheet 3.13.2 rx packet format the rx status words can be read from the rx status fifo port, while the rx data packets can be read from the rx data fifo. rx data packets are formatted in a specific manner before the host can read them as shown in figure 3.18 . it is assumed that the host ha s previously read the associated status word from the rx status fifo, to ascertain the data size and any error conditions. note 3.17 the LAN9215 host bus interface supports 16-bit bus transfers; internally, all data paths are 32-bits wide. figure 3.18 describes the host read ordering for pairs of atomic 16-bit transactions. 3.13.3 rx status format figure 3.18 rx packet format bits description 31 reserved. this bit is reserved. reads 0. 30 filtering fail. when set, this bit indicates that the associated frame failed the address recognizing filtering. 29:16 packet length. the size, in bytes, of the corresponding received frame. 15 error status (es). when set this bit indicates that the mil has reported an error. this bit is the internal logical ?or? of bits 11,7,6 and 1. 14 reserved. these bits are reserved. reads 0. 13 broadcast frame. when set, this bit indicates that the received frame has a broadcast address. ofs + first data dword . . . . last data dword 0 31 host read order 1st 2nd last optional pad dword0 . . optional pad dwordn optional offset dword0 . . optional offset dwordn
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet revision 2.9 (03-01-12) 62 smsc LAN9215 datasheet 3.13.4 stopping and starting the receiver to stop the receiver, the host must clear the rxen bit in the mac control register. when the receiver is halted, the rxstop_int will be pulsed. once st opped, the host can optiona lly clear the rx status and rx data fifos. the host must re-enable the receiver by setting the rxen bit. 3.13.5 receiver errors if the receiver error (rxe) flag is asserted for any reason, the receiver will continue operation. rx error (rxe) will be asserted under the following conditions: ? a host underrun of rx data fifo ? a host underrun of the rx status fifo ? an overrun of the rx status fifo it is the duty of the host to identi fy and resolve any error conditions. 12 length error (le). when set, this bit indicates that the actual length does not match with the length/type field of the received frame. 11 runt frame. when set, this bit indicates that frame was prematurely terminated before the collision window (64 bytes). runt frames are passed on to the host only if the pass bad frames bit mac_cr bit [16] is set. 10 multicast frame. when set, this bit indicates that t he received frame has a multicast address. 9:8 reserved. these bits are reserved. reads 0. 7 frame too long. when set, this bit indicates that the frame length exceeds the maximum ethernet specification of 1518 bytes. this is only a frame too long indication and will not cause the frame reception to be truncated. 6 collision seen. when set, this bit indicates that the fram e has seen a collision after the collision window. this indicates that a late collision has occurred. 5 frame type. when set, this bit indicates that the fram e is an ethernet-type frame (length/type field in the frame is greater than 1500). when reset, it indicates the incoming frame was an 802.3 type frame. this bit is not set for runt frames less than 14 bytes. 4 receive watchdog time-out. when set, this bit indicates that the incoming frame is greater than 2048 bytes through 2560 bytes, therefore expiring the receive watchdog timer. 3 mii error. when set, this bit indicates that a receive erro r (rx_er asserted) was detected during frame reception. 2 dribbling bit. when set, this bit indicates that the frame contained a non-integer multiple of 8 bits. this error is reported only if the number of dribbling bi ts in the last byte is 4 in the mii operating mode, or at least 3 in the 10 mbps oper ating mode. this bit will not be se t when the collision seen bit[6] is set. if set and the crc error bit[1] is cleared, then the packet is considered to be valid. 1 crc error. when set, this bit indicates that a crc error was detected. this bit is also set when the rx_er pin is asserted during the reception of a fr ame even though the crc may be correct. this bit is not valid if the received frame is a runt fram e, or a late collision was detected or when the watchdog time-out occurs. 0 reserved. these bits are reserved. reads 0 bits description
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet smsc LAN9215 63 revision 2.9 (03-01-12) datasheet chapter 4 internal ethernet phy 4.1 top level functional description functionally, the internal phy can be divided into the following sections: ? 100base-tx transmit and receive ? 10base-t transmit and receive ? internal mii interface to the ethernet media access controller ? auto-negotiation to automatically dete rmine the best speed and duplex possible ? management control to read status r egisters and write control registers figure 4.1 100base-tx data path 4.2 100base-tx transmit the data path of the 100base-tx is shown in figure 4.1 . each major block is explained below. 4.2.1 4b/5b encoding the transmit data passes from the mii block to th e 4b/5b encoder. this block encodes the data from 4-bit nibbles to 5-bit symbols (known as ?code-groups?) according to ta b l e 4 . 1 . each 4-bit data-nibble is mapped to 16 of the 32 possible code-groups. the remaining 16 code-groups are either used for control information or are not valid. the first 16 code-groups are referred to by the hexadecimal values of their corresponding data nibbles, 0 through f. the remaining code-groups are given le tter designations with slashes on either side. for example, an idle code-group is /i/, a tr ansmit error code-group is /h/, etc. the encoding process may be bypassed by clearing bit 6 of register 31. when the encoding is bypassed the 5 th transmit data bit is equivalent to tx_er. mac tx driver mlt-3 converter nrzi converter 4b/5b encoder magnetics cat-5 rj45 100m pll internal mii 25 mhz by 4 bits tx_clk 25mhz by 5 bits nrzi mlt-3 mlt-3 mlt-3 mlt-3 scrambler and piso 125 mbps serial mii 25mhz by 4 bits
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet revision 2.9 (03-01-12) 64 smsc LAN9215 datasheet table 4.1 4b/5b code table code group sym receiver interpretation transmitter interpretation 11110 0 0 0000 data 0 0000 data 01001 1 1 0001 1 0001 10100 2 2 0010 2 0010 10101 3 3 0011 3 0011 01010 4 4 0100 4 0100 01011 5 5 0101 5 0101 01110 6 6 0110 6 0110 01111 7 7 0111 7 0111 10010 8 8 1000 8 1000 10011 9 9 1001 9 1001 10110 a a 1010 a 1010 10111 b b 1011 b 1011 11010 c c 1100 c 1100 11011 d d 1101 d 1101 11100 e e 1110 e 1110 11101 f f 1111 f 1111 11111 i idle sent after /t/r until tx_en 11000 j first nibble of ssd, translated to ?0101? following idle, else rx_er sent for rising tx_en 10001 k second nibble of ssd, translated to ?0101? following j, else rx_er sent for rising tx_en 01101 t first nibble of esd, causes de-assertion of crs if followed by /r/, else assertion of rx_er sent for falling tx_en 00111 r second nibble of esd, causes deassertion of crs if following /t/, else assertion of rx_er sent for falling tx_en 00100 h transmit error symbol sent for rising tx_er 00110 v invalid, rx_er if during rx_dv invalid 11001 v invalid, rx_er if during rx_dv invalid 00000 v invalid, rx_er if during rx_dv invalid 00001 v invalid, rx_er if during rx_dv invalid 00010 v invalid, rx_er if during rx_dv invalid 00011 v invalid, rx_er if during rx_dv invalid
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet smsc LAN9215 65 revision 2.9 (03-01-12) datasheet 4.2.2 scrambling repeated data patterns (especially the idle code-grou p) can have power spectral densities with large narrow-band peaks. scrambling the data helps eliminate these peaks and spread the signal power more uniformly over the entire channel bandwidth. this uniform spectral density is required by fcc regulations to prevent excessive emi fr om being radiated by the physical wiring. the scrambler also performs the parallel in serial out conversion (piso) of the data. 4.2.3 nrzi and mlt3 encoding the scrambler block passes the 5-bit wide parallel data to the nrzi converter where it becomes a serial 125mhz nrzi data stream. the nrzi is encoded to mlt-3. mlt3 is a tri-level code where a change in the logic level represents a code bit ?1? and the logic output remaining at the same level represents a code bit ?0?. 4.2.4 100m transmit driver the mlt3 data is then passed to the analog transmitte r, which launches the differential mlt-3 signal, on outputs txp and txn, to the t wisted pair media via a 1:1 ratio isolation transformer. the 10base- t and 100base-tx signals pass through the same transformer so that common ?magnetics? can be used for both. the transmit ter drives into the 100 impedance of the cat-5 cable. cable termination and impedance matching require external components. 4.2.5 100m phase lock loop (pll) the 100m pll locks onto reference clock and genera tes the 125mhz clock used to drive the 125 mhz logic and the 100base-tx transmitter. 00101 v invalid, rx_er if during rx_dv invalid 01000 v invalid, rx_er if during rx_dv invalid 01100 v invalid, rx_er if during rx_dv invalid 10000 v invalid, rx_er if during rx_dv invalid table 4.1 4b/5b code table (continued) code group sym receiver interpretation transmitter interpretation
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet revision 2.9 (03-01-12) 66 smsc LAN9215 datasheet figure 4.2 receive data path 4.3 100base-tx receive the receive data path is shown in figure 4.2 . detailed descriptions are given below. 4.3.1 100m receive input the mlt-3 from the cable is fed into the phy (on inputs rxp and rxn) via a 1:1 ratio transformer. the adc samples the incoming differential signal at a rate of 125m samples per second. using a 64- level quanitizer it generates 6 digital bits to repr esent each sample. the dsp adjusts the gain of the adc according to the observed signal levels such t hat the full dynamic range of the adc can be used. 4.3.2 equalizer, baseline wander corr ection and clock and data recovery the 6 bits from the adc are fed into the dsp bl ock. the equalizer in the dsp section compensates for phase and amplitude distortion caused by the ph ysical channel consisting of magnetics, connectors, and cat- 5 cable. the equalizer can restore the signal for any good-quality cat-5 cable between 1m and 150m. if the dc content of the signal is such that the low-frequency comp onents fall below the low frequency pole of the isolation transformer, then the dro op characteristics of t he transformer will become significant and baseline wander (blw) on the receiv ed signal will result. to prevent corruption of the received data, the phy corrects for blw and c an receive the ansi x3.263-1995 fddi tp-pmd defined ?killer packet? with no bit errors. the 100m pll generates multiple phas es of the 125mhz clock. a mult iplexer, controlled by the timing unit of the dsp, selects the optimum phase for sa mpling the data. this is used as the received recovered clock. this clock is used to ex tract the serial data from the received signal. 4.3.3 nrzi and mlt-3 decoding the dsp generates the mlt-3 recovered levels that are fed to the mlt-3 converter. the mlt-3 is then converted to an nrzi data stream. mac a/d converter mlt-3 converter nrzi converter 4b/5b decoder magnetics cat-5 rj45 100m pll internal mii 25mhz by 4 bits rx_clk 25mhz by 5 bits nrzi mlt-3 mlt-3 mlt-3 6 bit data descrambler and sipo 125 mbps serial dsp: timing recovery, equalizer and blw correction mlt-3 mii 25mhz by 4 bits
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet smsc LAN9215 67 revision 2.9 (03-01-12) datasheet 4.3.4 descrambling the descrambler performs an inverse function to t he scrambler in the transmitter and also performs the serial in parallel out (sipo) conversion of the data. during reception of idle (/i/) symbols. the descrambler synchron izes its descrambler key to the incoming stream. once synchronizati on is achieved, the descrambler locks on this key and is able to descramble incoming data. special logic in the descrambler ensures synchronization with the remote phy by searching for idle symbols within a window of 4000 bytes (40us). th is window ensures that a maximum packet size of 1514 bytes, allowed by the ieee 802. 3 standard, can be received with no interference. if no idle- symbols are detected within this time-period, rece ive operation is aborted and the descrambler re-starts the synchronization process. the descrambler can be bypassed by setting bit 0 of register 31. 4.3.5 alignment the de-scrambled signal is then aligned into 5-bit code-groups by recognizing the /j/k/ start-of-stream delimiter (ssd) pair at the start of a packet. once the code-word alignment is determined, it is stored and utilized until the next start of frame. 4.3.6 5b/4b decoding the 5-bit code-groups are translated into 4-bit data nibbles according to the 4b/5b table. the ssd, /j/k/, is translated to ?0101 0101? as the first 2 nibbles of the mac preamble. reception of the ssd causes the phy to assert the internal rx_dv signal , indicating that valid data is available on the internal rxd bus. successive valid code-groups are tran slated to data nibbles. reception of either the end of stream delimiter (esd) consisting of the /t /r/ symbols, or at least two /i/ symbols causes the phy to de-assert the internal carrier sense and rx_dv. these symbols are not translated into data. 4.4 10base-t transmit data to be transmitted comes from the mac layer co ntroller. the 10base-t transmitter receives 4-bit nibbles from the mii at a rate of 2.5mhz and converts them to a 10mbps serial data stream. the data stream is then manchester-encoded and sent to the analog transmitter, which drives a signal onto the twisted pair via the external magnetics. the 10m transmitter uses the following blocks: ? mii (digital) ? tx 10m (digital) ? 10m transmitter (analog) ? 10m pll (analog) 4.4.1 10m transmit data across the internal mii bus the mac controller drives the transmit data onto the internal txd bus. when the controller has driven tx_en high to indicate valid data, the data is latched by the mii block on the rising edge of tx_clk. the data is in the form of 4-bit wide 2.5mhz data. 4.4.2 manchester encoding the 4-bit wide data is sent to the tx10m block. th e nibbles are converted to a 10mbps serial nrzi data stream. the 10m pll locks onto the external cl ock or internal oscillator and produces a 20mhz
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet revision 2.9 (03-01-12) 68 smsc LAN9215 datasheet clock. this is used to manchester encode the nrz data stream. when no data is being transmitted (tx_en is low), the tx10m block outputs normal link pulses (nlps) to maintain communications with the remote link partner. 4.4.3 10m transmit drivers the manchester encoded data is sent to the anal og transmitter where it is shaped and filtered before being driven out as a differential signal across the txp and txn outputs. 4.5 10base-t receive the 10base-t receiver gets the manchester- encoded analog signal from the cable via the magnetics. it recovers the receive clock from the signal and uses this clock to recover the nrzi data stream. this 10m serial data is converted to 4-bit data nibbles which are passed to the controller across the mii at a rate of 2.5mhz. this 10m receiver uses the following blocks: ? filter and squelch (analog) ? 10m pll (analog) ? rx 10m (digital) ? mii (digital) 4.5.1 10m receive input and squelch the manchester signal from the cable is fed into the phy (on inputs rxp and rxn) via 1:1 ratio magnetics. it is first filtered to reduce any out-of-band noise. it then passes through a squelch circuit. the squelch is a set of amplitude and timi ng comparators that norma lly reject differential voltage levels below 300mv and detect and re cognize differential voltages above 585mv. 4.5.2 manchester decoding the output of the squelch goes to the rx10m block where it is validated as manchester encoded data. the polarity of the signal is also checked. if the polarity is reversed (local rxp is connected to rxn of the remote partner and vice versa), then this is identified and corrected. the reversed condition is indicated by the flag ?xpol?, bit 4 in register 27. the 10m pll is locked onto the received manchester signal and from this, generates the received 20mhz clock. using this clock, the manchester encoded data is extracted and conver ted to a 10mhz nrzi dat a stream. it is then converted from serial to 4-bit wide parallel data. the rx10m block also detects valid 10base-t idle signals - normal link pulses (nlps) - to maintain the link. 4.5.3 jabber detection jabber is a condition in which a station transmits for a period of time longer than the maximum permissible packet length, usually due to a fault condi tion, that results in ho lding the tx_en input for a long period. special logic is used to detect the jabber state and abort the transmission to the line, within 45ms. once tx_en is deasserted, the logic resets the jabber condition. 4.6 auto-negotiation the purpose of the auto-negotiation function is to automatically configure the phy to the optimum link parameters based on the capabilities of its li nk partner. auto-negotiation is a mechanism for exchanging configuration information between two lin k-partners and automatically selecting the highest
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet smsc LAN9215 69 revision 2.9 (03-01-12) datasheet performance mode of operation supported by both si des. auto-negotiation is fully defined in clause 28 of the ieee 802.3 specification. once auto-negotiation has completed, information ab out the resolved link can be passed back to the controller via the internal serial management interf ace (smi). the results of the negotiation process are reflected in the speed indication bits in register 31, as well as the link partner ability register (register 5). the auto-negotiation protocol is a purely physical layer activity and proceeds independently of the mac controller. the advertised capabilities of the phy are stored in register 4 of the sm i registers. the default advertised by the phy is determined by user-defined on-chip signal options. the following blocks are activated during an auto-negotiation session: ? auto-negotiation (digital) ? 100m adc (analog) ? 100m pll (analog) ? 100m equalizer/blw/clock recovery (dsp) ? 10m squelch (analog) ? 10m pll (analog) ? 10m transmitter (analog) when enabled, auto-negotiation is started by t he occurrence of one of the following events: ? hardware reset ? software reset ? power-down reset ? link status down ? setting register 0, bit 9 high (auto-negotiation restart) on detection of one of these event s, the phy begins auto-negotiation by transmitting bursts of fast link pulses (flp). these are bur sts of link pulses from the 10m transmitter. they are shaped as normal link pulses and can pass uncorrupted down cat-3 or cat-5 cable. a fast link pulse burst consists of up to 33 pulses. the 17 odd-number ed pulses, which are always present, frame the flp burst. the 16 even-numbered pulses, which may be present or absent, cont ain the data word being transmitted. presence of a data pulse repres ents a ?1?, while absence represents a ?0?. the data transmitted by an flp burst is known as a ?link code word.? these are defined fully in ieee 802.3 clause 28. in summary, the phy advertises 8 02.3 compliance in its selector field (the first 5 bits of the link code word). it advertises its technology abi lity according to the bits set in register 4 of the smi registers. there are 4 possible matches of the technology ab ilities. in the order of priority these are: ? 100m full-duplex (highest priority) ? 100m half-duplex ? 10m full-duplex ? 10m half-duplex if the full capabilities of the phy are advertised (100 m, full-duplex), and if the link partner is capable of 10m and 100m, then auto-negotiation selects 1 00m as the highest performance mode. if the link partner is capable of half and full-duplex modes, th en auto-negotiation selects full-duplex as the highest performance operation.
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet revision 2.9 (03-01-12) 70 smsc LAN9215 datasheet once a capability match has been determined, the link code words are repeated with the acknowledge bit set. any difference in the main content of the link code words at this time will cause auto-negotiation to re-start. auto-negotiation will also re-start if not all of the required flp bursts are received. writing register 4 bits [8:5] allows software control of the capabilities advertised by the phy. writing register 4 does not automatically re -start auto-negotiation. register 0, bit 9 must be set before the new abilities will be advertised. auto-negotiation can also be disabled via software by clearing register 0, bit 12. the LAN9215 does not support ?next page" capability. 4.7 parallel detection if the LAN9215 is connected to a device lacking the ability to auto-negotiate (i.e. no flps are detected), it is able to determi ne the speed of the link based on either 100m mlt-3 symbols or 10m normal link pulses. in this case the link is pres umed to be half-duplex per the ieee standard. this ability is known as ?parallel detection. this featur e ensures inter operability with legacy link partners. if a link is formed via parallel detection, then bit 0 in register 6 is cleared to indicate that the link partner is not capable of auto-n egotiation. the ethernet mac has access to this information via the management interface. if a fault occurs during pa rallel detection, bit 4 of register 6 is set. register 5 is used to store the link partner abilit y information, which is coded in the received flps. if the link partner is not auto-negotiation capable, then register 5 is updated after completion of parallel detection to reflect the speed capability of the link partner. 4.7.1 re-starting auto-negotiation auto-negotiation can be re-started at any time by sett ing register 0, bit 9. auto-negotiation will also re- start if the link is broken at any time. a broken link is caused by signal loss. this may occur because of a cable break, or because of an interruption in the signal transmitted by the link partner. auto- negotiation resumes in an attempt to determine the new link configuration. if the management entity re-starts au to-negotiation by writing to bi t 9 of the control register, the LAN9215 will respond by stopping all transmission/rec eiving operations. once the break_link_timer is done, in the auto-negotiation state-machine (appro ximately 1200ms) the auto-negotiation will re-start. the link partner will have also dropped the link due to lack of a received signal, so it too will resume auto-negotiation. 4.7.2 disabling auto-negotiation auto-negotiation can be disabled by setting regist er 0, bit 12 to zero. the device will then force its speed of operation to reflect the information in regist er 0, bit 13 (speed) and register 0, bit 8 (duplex). the speed and duplex bits in register 0 should be ignored when auto-negotiation is enabled. 4.7.3 half vs. full-duplex half-duplex operation relies on the csma/cd (carrier sense multiple access / collision detect) protocol to handle network traffic and collisions. in this mode, the internal carrier sense signal, crs, responds to both transmit and receive activity. in this mode, if data is received while the phy is transmitting, a collision results. in full-duplex mode, the phy is able to transmit and receive data simultaneously. in this mode, the internal crs responds only to receive activity. the csma/cd protocol does not apply and collision detection is disabled. table 4.2 describes the behavior of the internal crs bit under all receive/transmit conditions. the internal crs signal is used to trigger bit 10 (no carrier) of the tx status word (see section 3.12.4, "tx status format" ). the crs value, and subsequ ently the no carrier value, are invalid during any
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet smsc LAN9215 71 revision 2.9 (03-01-12) datasheet full-duplex transmission. therefore, these si gnals cannot be used as a verification method of transmitted packets when transmitting in 10/100 mbps full-duplex modes. note 4.1 the LAN9215 10/100 phy internal crs signal operates in two modes: active and low. when in active mode, the internal crs will transition high and low upon line activity, where a high value indicates a carrier has been detec ted. in low mode, t he internal crs stays low and does not indicate carrier detection. the internal crs signal and no carrier (bit 10 of the tx status word) cannot be used as a verification method of transmitted packets when transmitting in 10/100 mbps full-duplex mode. 4.8 hp auto-mdix hp auto-mdix facilitates the use of cat-3 (10 base -t) or cat-5 (100 base-t ) media utp interconnect cable without consideration of inte rface wiring scheme. if a user plugs in either a direct connect lan cable, or a cross-over patch cable, as shown in figure 4.3 , the smsc LAN9215 auto-mdix phy is capable of configuring the tpo and tpi twisted pair pins for correct transceiver operation. the internal logic of the device detects the tx and rx pins of the connecting device. since the rx and tx line pairs are interchangeable, special pcb design considerations are needed to accommodate the symmetrical magnetics and termination of an auto-mdix design. the auto-mdix function can be disabled through an inte rnal register 27.15, or the external control pins amdix_en. when disabled the tx and rx pins can be configured with the channel select (ch_select) pin as desired. table 4.2 crs behavior mode speed duplex activity crs behavior ( note 4.1 ) manual 10 mbps half-duplex transmitting active manual 10 mbps half-duplex receiving active manual 10 mbps full-duplex transmitting low manual 10 mbps full-duplex receiving active manual 100 mbps half-duplex transmitting active manual 100 mbps half-duplex receiving active manual 100 mbps full-duplex transmitting low manual 100 mbps full-duplex receiving active auto-negotiation 10 mbps half-duplex transmitting active auto-negotiation 10 mbps half-duplex receiving active auto-negotiation 10 mbps full-duplex transmitting low auto-negotiation 10 mbps full-duplex receiving active auto-negotiation 100 mbps half-duplex transmitting active auto-negotiation 100 mbps half-duplex receiving active auto-negotiation 100 mbps full-duplex transmitting low auto-negotiation 100 mbps full-duplex receiving active
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet revision 2.9 (03-01-12) 72 smsc LAN9215 datasheet the figure below shows the signal names at the rj-45 connector, the mapping of these signals to the pins on the LAN9215 is as follows: txp = tpo+ txn = tpo- rxp = tpi+ rxn = tpi- figure 4.3 direct cable connection vs. cross-over cable connection
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet smsc LAN9215 73 revision 2.9 (03-01-12) datasheet chapter 5 register description the following section describes all LAN9215 registers and data ports. note: the LAN9215 host bus interface supports 16-bit bus transfers; internally, all data paths are 32- bits wide. figure 5.1 describes the memory map with respect to pairs of atomic 16-bit transactions. figure 5.1 memory map mac csr port a4h b0h base + 00h reserved b4h a0h rx data fifo port tx data fifo port rx status fifo por t 40h 20h 50h fch eeprom port 04h 1ch rx dat a fifo alias po r t s 24h 3ch tx data fifo alias por ts rx status fifo peek 44h tx status fifo port 48h tx status fifo peek 4ch a8h ach
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet revision 2.9 (03-01-12) 74 smsc LAN9215 datasheet 5.1 register nomenclatu re and access attributes 5.2 rx and tx fifo ports the LAN9215 contains four host-ac cessible fifos: rx status, rx data, tx status, and tx data fifos. the sizes data fifos and the rx stat us fifo are configurable through the csrs. 5.2.1 rx fifo ports the rx data path contains two read-only fifos: rx status and rx data. the rx status fifo has two ports at different address locations. the rx stat us fifo port causes t he top of the rx status fifo to be ?popped?, and is destructive. the rx status fifo peek port allows the top of the rx status fifo to be read without ?popping? it. the rx data fifo has a single port; reading data from this port always causes the top of the rx data fifo to be ?popped?. this port is aliased to 16 word locations. the host may access the top of the rx data fifo through any of these locations. 5.2.2 tx fifo ports the tx data path consists of two fifos, tx stat us and rx data. the tx st atus fifo also has two ports at different locations. when the tx status fifo port is read, the top of the tx status fifo is popped. when the tx status fifo peek port is read, the top of the tx status fifo is not popped. the tx data fifo is write only. it is aliased to 16 word locations . the host may access the top of the tx data fifo through any of these locations. symbol description ro read only: if a register is read only, writ es to this register have no effect. wo write only: if a register is write only, reads always return 0. r/w read/write: a register with this attri bute can be read and written r/wc read/write clear: a register bit with this attribute can be read and written. however, a write of a 1 clears (sets to 0) the corresponding bit and a write of a 0 has no effect. rc read to clear: a register bit with this attribute is cleared when read. ll latch low: clear on read of register lh latch high: clear on read of register sc self-clearing nasr not affected by software reset reserved bits certain bits within registers are listed as ?reser ved?. unless stated otherwise, these bits must be written with zeros for futu re compatibility. the values of these bits are not guaranteed when read. reserved registers certain configuration registers within the LAN9215 are listed as ?reserved?. these registers are not guaranteed to return any particular value when re ad. these registers must not be written to or modified by system failure; doing so could result in failure of the device and system. default states at reset - system reset, software reset, or por - internal registers are set to their default states. the default states provide a minimum level of fu nctionality needed to successfully bring up a system, but do not necessarily provide desired or optimal conf iguration of the device. it is the responsibility of the system initialization software to properly determine the operating parameters and optional system features that are applicable, and to program th e LAN9215 registers accordingly.
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet smsc LAN9215 75 revision 2.9 (03-01-12) datasheet 5.3 system contro l and status registers table 5.1, "direct address register map" , lists the registers that are directly addressable by the host bus. table 5.1 direct address register map control and status registers base address + offset symbol register name default 50h id_rev chip id and revision. see page 76. 54h irq_cfg main interrupt configuration 00000000h 58h int_sts interrupt status 00000000h 5ch int_en interrupt enable register 00000000h 60h reserved reserved for future use - 64h byte_test read-only byte order testing register 87654321h 68h fifo_int fifo level interrupts 48000000h 6ch rx_cfg receive configuration 00000000h 70h tx_cfg transmit configuration 00000000h 74h hw_cfg hardware configuration 00050000h 78h rx_dp_ctl rx datapath control 00000000h 7ch rx_fifo_inf receive fifo information 00000000h 80h tx_fifo_inf transmit fifo information 00001200h 84h pmt_ctrl power management control 00000000h 88h gpio_cfg general purpose io configuration 00000000h 8ch gpt_cfg general purpose timer configuration 0000ffffh 90h gpt_cnt general purpose timer count 0000ffffh 94h reserved reserved for future use - 98h word_swap word swap register 00000000h 9ch free_run free run counter - a0h rx_drop rx dropped frames counter 00000000h a4h mac_csr_cmd mac csr synchronizer command (mac csr?s are indexed through this register) 00000000h a8h mac_csr_data mac csr synchronizer data 00000000h ach afc_cfg automatic flow control configuration 00000000h b0h e2p_cmd eeprom command 00000000h b4h e2p_data eeprom data 00000000h b8h - fch reserved reserved for future use -
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet revision 2.9 (03-01-12) 76 smsc LAN9215 datasheet 5.3.1 id_rev?chip id and revision this register contains the id and revision fields for this design. 5.3.2 irq_cfg?interrupt configuration register this register configures and indi cates the state of the irq signal. offset: 50h size: 32 bits bits description type default 31-16 chip id. this read-only field identifies this design ro 115ah 15-0 chip revision ro 0000h offset: 54h size: 32 bits bits description type default 31:24 interrupt deassertion interval (int_deas). this field determines the interrupt request deassertion interval in multiples of 10 microseconds. setting this field to zero causes the device to disable the int_deas interval, reset the interval counter, and issue any pending interrupts. if a new, non-zero value is written to this field, any subsequent interrupts will obey the new setting. note: this field does not apply to the pme interrupt. r/w 0 23-15 reserved ro - 14 interrupt deassertion interval clear (int_deas_clr ). writing a one to this register clears the de-asserti on counter in the irq controller, thus causing a new de-assertion interval to begin (regardless of whether or not the irq controller is currently in an active de-assertion interval). sc 0 13 interrupt deassertion status (int_deas_sts). when set, this bit indicates that interrupts are currently in a deassertion interval, and will not be delivered to the irq pin. when this bit is clear, interrupts are not currently in a deassertion interval, and will be delivered to the irq pin. sc 0 12 master interrupt (irq_int). this read-only bit indicates the state of the internal irq line, regardless of the se tting of the irq_en bit, or the state of the interrupt de-assertion function. when this bit is high, one of the enabled interrupts is currently active. ro 0 11-9 reserved ro - 8 irq enable (irq_en) ? this bit controls the final interrupt output to the irq pin. when clear, the irq output is disabled and permanently deasserted. this bit has no effect on any internal interrupt status bits. r/w 0 7-5 reserved ro -
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet smsc LAN9215 77 revision 2.9 (03-01-12) datasheet 4 irq polarity (irq_pol) ? when cleared, enables the irq line to function as an active low output. when set, the irq output is active high. when irq is configured as an open- drain output this field is ignored, and the interrupt output is always active low. r/w nasr 0 3-1 reserved ro - 0 irq buffer type (irq_type) ? when cleared, enables irq to function as an open-drain buffer for use in a wired-or interrupt configuration. when set, the irq output is a push-pull driver. when configured as an open-drain output the irq_pol field is ignored, and the interrupt output is always active low. r/w nasr 0 bits description type default
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet revision 2.9 (03-01-12) 78 smsc LAN9215 datasheet 5.3.3 int_sts?interrupt status register this register contains the current status of the generated interrupts. writing a 1 to the corresponding bits acknowledges and clears the interrupt. offset: 58h size: 32 bits bits description type default 31 software interrupt (sw_int). this interrupt is generated when the sw_int_en bit is set high. writing a one clears this interrupt. r/wc 0 30-26 reserved ro - 25 tx stopped (txstop_int). this interrupt is issued when stop_tx bit in tx_cfg is set, and the transmitter is halted. r/wc 0 24 rx stopped (rxstop_int). t his interrupt is issued when the receiver is halted. r/wc 0 23 rx dropped frame counter halfway (rxdfh_int). this interrupt is issued when the rx dropped frames counter counts past its halfway point (7fffffffh to 80000000h). r/wc 0 22 reserved ro 0 21 tx ioc interrupt (tx_ioc). when a buffer with the ioc flag set has finished being loaded into the tx fifo, this interrupt is generated. r/wc 0 20 rx dma interrupt (rxd_int). this interrupt is issued when the amount of data programmed in the rx dma count (rx_dma_cnt) field of the rx_cfg register has been transferred out of the rx fifo. r/wc 0 19 gp timer (gpt_int). this interrupt is issued when the general purpose timer wraps past zero to ffffh. r/wc 0 18 phy (phy_int). indicates a phy interrupt event. ro 0 17 power management even t interrupt (pme_int). this interrupt is issued when a power management event is detected as configured in the pmt_ctrl register. this interrupt functions independent of the pme signal, and will still function if the pme signal is disabled. writing a '1' clears this bit regardless of the state of the pme hardware signal. notes: ? detection of a power management event, and assertion of the pme signal will not wakeup the LAN9215. the LAN9215 will only wake up when it detects a host write cycl e of any data to the byte_test register. ? the interrupt deassertion interval does not apply to the pme interrupt. r/wc 0 16 tx status fifo overflow (txso). generated when the tx status fifo overflows. r/wc 0 15 receive watchdog time-out (rwt). interrupt is generated when a packet larger than 2048 bytes has been received. r/wc 0 14 receiver error (rxe). indicates that the receiver has encountered an error. please refer to section 3.13.5, "receiver errors," on page 62 for a description of the conditions that will cause an rxe. r/wc 0 13 transmitter error (txe). when generated, indicates that the transmitter has encountered an error. please refer to section 3.12.7, "transmitter errors," on page 58 , for a description of the conditions that will cause a txe. r/wc 0
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet smsc LAN9215 79 revision 2.9 (03-01-12) datasheet 12:11 reserved ro - 10 tx data fifo overrun interrupt (tdfo). generated when the tx data fifo is full, and anothe r write is attempted. r/wc 0 9 tx data fifo available interrupt (tdfa). generated when the tx data fifo available space is greater than the programmed level. r/wc 0 8 tx status fifo full interrupt (tsff). generated when the tx status fifo is full. r/wc 0 7 tx status fifo level interrupt (tsfl). generated when the tx status fifo reaches the programmed level. r/wc 0 6 rx dropped frame interrupt (rxdf_int). this interrupt is issued whenever a receive frame is dropped. r/wc 0 5 reserved ro - 4 rx status fifo full interrupt (rsff). generated when the rx status fifo is full. r/wc 0 3 rx status fifo level interrupt (rsfl). generated when the rx status fifo reaches the programmed level. r/wc 0 2-0 gpio [2:0] (gpiox_int). interrupts are generated from the gpio?s. these interrupts are configured through the gpio_cfg register. r/wc 000 bits description type default
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet revision 2.9 (03-01-12) 80 smsc LAN9215 datasheet 5.3.4 int_en?interrupt enable register this register cont ains the interrupt masks for irq. writin g 1 to any of the bits enables the corresponding interrupt as a source for irq. bits in the int_sts register will still reflect the status of the interrupt source regardless of whether the sour ce is enabled as an interrupt in this register. offset: 5ch size: 32 bits bits descriptio n type default 31 software interrupt (sw_int_en) r/w 0 30:26 reserved ro - 25 tx stopped interrupt enable (txstop_int_en) r/w 0 24 rx stopped interrupt enable (rxstop_int_en) r/w 0 23 rx dropped frame counter halfway in terrupt enable (rxdfh_int_en). r/w 0 22 reserved ro 0 21 tx ioc interrupt enable (tioc_int_en) r/w 0 20 rx dma interrupt (rxd_int). r/w 0 19 gp timer (gpt_int_en) r/w 0 18 phy (phy_int_en) r/w 0 17 power management event inte rrupt enable (pme_int_en) r/w 0 16 tx status fifo overflow (txso_en) r/w 0 15 receive watchdog time-out interrupt (rwt_int_en) r/w 0 14 receiver error interrupt (rxe_int_en) r/w 0 13 transmitter error inte rrupt (txe_int_en) r/w 0 12:11 reserved ro - 10 tx data fifo overrun in terrupt (tdfo_int_en) r/w 0 9 tx data fifo available interrupt (tdfa_int_en) r/w 0 8 tx status fifo full interrupt (tsff_int_en) r/w 0 7 tx status fifo level interrupt (tsfl_int_en) r/w 0 6 rx dropped frame interrupt enable (rxdf_int_en) r/w 0 5 reserved ro - 4 rx status fifo full interrupt (rsff_int_en) r/w 0 3 rx status fifo level interrupt (rsfl_int_en) r/w 0 2-0 gpio [2:0] (gpiox_int_en). r/w 000
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet smsc LAN9215 81 revision 2.9 (03-01-12) datasheet 5.3.5 byte_test?byte order test register this register can be used to determine t he byte ordering of the current configuration 5.3.6 fifo_int?fifo level interrupts this register configures the li mits where the fifo controllers will generate system interrupts. offset: 64h size: 32 bits bits description type default 31:0 byte test ro 87654321h offset: 68h size: 32 bits bits description type default 31-24 tx data available level. the value in this field sets the level, in number of 64 byte blocks, at wh ich the tx fifo available interrupt (tfda) will be generated. when the tx data fifo fr ee space is greater than this value a tx fifo available interrupt (tdfa) will be generated. r/w 48h 23-16 tx status level. the value in this field sets the level, in number of dwords, at which the tx status fi fo level interrupt (tsfl) will be generated. when the tx stat us fifo used space is greater than this value an tx status fifo level interr upt (tsfl) will be generated. r/w 00h 15-8 reserved ro - 7-0 rx status level. the value in this field sets the level, in number of dwords, at which the rx status fi fo level interrupt (rsfl) will be generated. when the rx status fifo used space is greater than this value an rx status fifo level interrupt (rsfl) will be generated. r/w 00h
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet revision 2.9 (03-01-12) 82 smsc LAN9215 datasheet 5.3.7 rx_cfg?receive configuration register this register controls the LAN9215 receive engine. offset: 6ch size: 32 bits bits description type default 31:30 rx end alignment. this field specifies the alignment that must be maintained on the last data transfer of a buffer. the LAN9215 will add extra dwords of data up to the alignment specified in the table below. the host is responsible for removing these extra dwords. this mechanism can be used to maintain cache line alignment on host processors. please refer to ta b l e 5 . 2 for bit definitions note: the desired rx end alignment must be set before reading a packet. the rx end alignment can be changed between reading receive packets, but must not be changed if the packet is partially read. r/w 00b 29-28 reserved ro - 27-16 rx dma count (rx_dma_cnt). this 12-bit field indicates the amount of data, in dwords, to be transferred out of the rx data fifo before asserting the rxd_int. after being set, this field is decremented for each dword of data that is read from t he rx data fifo. this field can be overwritten with a new value before it reaches zero. r/w 000h 15 force rx discard (rx_dump). this self-clearing bit clears the rx data and status fifos of all pending data. when a ?1? is written, the rx data and status pointers are cleared to zero. note: please refer to section ?force receiver discard (receiver dump)? on page 60 for a detailed description regarding the use of rx_dump. sc 0 14-13 reserved ro - 12-8 rx data offset (rxdoff). this field controls the offset value, in bytes, that is added to the beginning of an rx data packet. the start of the valid data will be shifted by the number of byte s specified in this field. an offset of 0-31 bytes is a valid number of offset bytes. note: the two lsbs of this field (d[9 :8]) must not be modified while the rx is running. the receiver must be halted, and all data purged before these two bits can be modified. the upper three bits (dword offset) may be modified while the receiver is running. modifications to the upper bits will take affect on the next dword read. r/w 00000 7-0 reserved ro - table 5.2 rx alignm ent bit definitions [31] [30] end alignment 0 0 4-byte alignment 0 1 16-byte alignment 1 0 32-byte alignment 11 reserved
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet smsc LAN9215 83 revision 2.9 (03-01-12) datasheet 5.3.8 tx_cfg?transmit configuration register this register controls t he transmit functions on the LAN9215 ethernet controller. offset: 70h size: 32 bits bits description type default 31-16 reserved. ro - 15 force tx status discard (txs_dump). this self-clearing bit clears the tx status fifo of all pending status dword?s. when a ?1? is written, the tx status pointers are cleared to zero. sc 0 14 force tx data discard (txd_dump). this self-clearing bit clears the tx data fifo of all pending data. when a ?1 ? is written, the tx data pointers are cleared to zero. sc 0 13-3 reserved ro - 2 tx status allow overrun (txsao). when this bit is cleared, data transmission is suspended if the tx st atus fifo becomes full. setting this bit high allows the transmitter to cont inue operation with a full tx status fifo. note: this bit does not affect the operat ion of the tx status fifo full interrupt. r/w 0 1 transmitter en able (tx_on). when this bit is set (1), the transmitter is enabled. any data in the tx fifo will be sent. this bit is cleared automatically when stop_tx is se t and the transmitter is halted. r/w 0 0 stop transmitter (stop_tx). when this bit is set (1), the transmitter will finish the current frame, and will then stop transmitting. when the transmitter has stopped this bit will clear. all writes to this bit are ignored while this bit is high. sc 0
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet revision 2.9 (03-01-12) 84 smsc LAN9215 datasheet 5.3.9 hw_cfg?hardware configuration register note: the transmitter and receiver must be stopped be fore writing to this register. refer to section 3.12.8, "stopping and starting the transmitter," on page 58 and section 3.13.4, "stopping and starting the receiver," on page 62 for details on stopping the transmitter and receiver. offset: 74h size: 32 bits bits description type default 31-25 reserved ro - 24 amdix_en strap state . this read-only bit reflects the state of the amdix_en strap pin (pin 73). this pin can be overridden by phy registers 27.15 and 27.13 ro amdix strap pin 23-21 reserved ro - 20 must be one (mbo). this bit must be set to ?1? for normal device operation. r/w 0 16-19 tx fifo size (tx_fif_sz). sets the size of the tx fifos in 1kb values to a maximum of 14kb. the tx status fifo consumes 512 bytes of the space allocated by tx_fif_siz, and the tx data fifo consumes the remaining space specified by tx_fif _sz. the minimum size of the tx fifos is 2kb (tx data and status combi ned). the tx data fifo is used for both tx data and tx commands. the rx status and data fifos consume the remaining space, which is equal to 16kb ? tx_fif_siz. see section 5.3.9.1, "allowable settings for configurable fifo memory allocation," on page 86 for more information. r/w 5h 15-7 reserved ro - 6-5 phy clock select (phy_clk_sel). this field is used to switch between the internal and ex ternal mii clocks (rx_clk and tx_clk). this field is encoded as follows: [6] [5] mii clock source --------------------------------------------------- 0 0 internal phy 0 1 external mii port 1 0 clocks disabled 1 1 internal phy notes: ? this field does not control multiplexing of the smi port or other mii signals. ? there are restrictions on the use of this field. please refer to section 3.11, "mii interface - external mii switching," on page 46 for details. r/w 00b 4 serial management inte rface select (smi_sel ). this bit is used to switch the smi port (mdio and mdc) between the internal phy and the external mii port. when this bit is cleared to ?0 ?, the internal phy is selected, and all smi transactions will be to the internal phy. when this bit is set to ?1?, the external mii port is sele cted, and all smi transactions will be to the external phy. this bit functions independent of ext_phy_en. when this bit is set, the internal mdio and mdc signals are driven low. when this bit is cleared, the external midio signal is tri-st ated, and the mdc signal is driven low. note: this bit does not control the mult iplexing of other mii signals. r/w 0
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet smsc LAN9215 85 revision 2.9 (03-01-12) datasheet 3 external phy detect (ext_phy_det) . this bit reflects the latched value of the ext_phy_det strap. the ext_phy_det strap is used to indicate the presence of an external phy. this strap is latched from the value of the external mdio signal upon power-up or hard reset. if mdio is pulled high a ?1? will be seen in this bit. if mdio is pulled low a ?0? will be seen in this bit. the ext_phy_det strap has no other effect on the internal logic. its only function is to give th e system designer a mechan ism to indicate the presence of an external phy to a software application. ro dependant on ext_phy_d et strap pin 2 external phy enable (ext_phy_en ). when set to a ?1?, this bit enables the external mii port. when cleared, the internal phy is enabled and the external mii port is disabled. notes: ? this signal does not control multiple xing of the smi port or the tx_clk or rx_clk signals. ? there are restrictions on the us e of this bit. please refer to section 3.11, "mii interface - external mii switching," on page 46 for details. rw 0 1 soft reset timeout (srst_to) . if a software reset is attempted when the internal phy is not in the operational state (rx_clk and tx_clk running), the reset will not complete and the soft reset operation will timeout and this bit will be set to a ?1?. the host processor must correct the problem and issue another soft reset. ro 0 0 soft reset (srst) . writing 1 generates a software initiated reset. this reset generates a full reset of the mac csr?s. the scsr?s (system command and status registers) are reset except for any nasr bits. soft reset also clears any tx or rx errors (txe/rxe). this bit is self-clearing. notes: ? do not attempt a soft reset unless the internal phy is fully awake and operational. after a phy reset, or when returning from a reduced power state, the phy must given adequate time to return to the operational state before a soft reset can be issued. the internal rx_clk and tx_clk signals must be running for a proper software reset. please refer to section 6.8, "reset timing," on page 131 for details on phy reset timing. ? the LAN9215 must always be read at least once after power-up, reset, or upon return from a power-saving state or write operations will not function. sc 0 bits description type default
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet revision 2.9 (03-01-12) 86 smsc LAN9215 datasheet 5.3.9.1 allowable settings for conf igurable fifo memory allocation tx and rx fifo space is configurable through th e csr - hw_cfg register defined above. the user must select the fifo allocation by setting the tx fifo size (tx_fif_sz) field in the hardware configuration (hw_cfg) register. th e tx_fif_sz field selects the total allocation for the tx data path, including the tx status fifo size. the tx status fifo size is fixed at 512 bytes (128 tx status dwords). the tx status fifo length is subtract ed from the total tx fifo size with the remainder being the tx data fifo size. note that tx dat a fifo space includes both commands and payload data. rx fifo size is the remainder of the unallocat ed fifo space (16384 bytes ? tx fifo size). the rx status fifo size is always equal to 1/16 of the rx fifo size. the rx status fifo length is subtracted from the total rx fifo size with the remainder being the rx data fifo size. for example, if tx_fif_sz = 6 then: total tx fifo size = 6144 bytes (6kb) tx status fifo size = 512 bytes (fixed) tx data fifo size = 6144 ? 512 = 5632 bytes rx fifo size = 16384 ? 6144 = 10240 bytes (10kb) rx status fifo size = 10240 / 16 = 640 bytes (160 rx status dwords) rx data fifo size = 10240 ? 640 = 9600 bytes table 5.3 shows every valid setting for t he tx_fif_sz field. note that se ttings not shown in this table are reserved and should not be used. note: the rx data fifo is considered full 4 dwords before the length that is specified in the hw_cfg register. table 5.3 valid tx/rx fifo allocations tx_fif_sz tx data fifo size (bytes) tx status fifo size (bytes) rx data fifo size (bytes) rx status fifo size (bytes) 2 1536 512 13440 896 3 2560 512 12480 832 4 3584 512 11520 768 5 4608 512 10560 704 6 5632 512 9600 640 7 6656 512 8640 576 8 7680 512 7680 512 9 8704 512 6720 448 10 9728 512 5760 384 11 10752 512 4800 320 12 11776 512 3840 256 13 12800 512 2880 192 14 13824 512 1920 128
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet smsc LAN9215 87 revision 2.9 (03-01-12) datasheet in addition to the host-accessible fifos, the mac interface layer (mil) contains an additional 2k bytes of tx, and 128 bytes of rx fifo buffering. th ese sizes are fixed, and cannot be adjusted by the host. as space in the tx mil (mac interface layer) fifo frees, data is moved into it from the tx data fifo. depending on the size of the frames to be transmitt ed, the mil can hold up to two ethernet frames. this is in addition to any tx data that may be queued in the tx data fifo. conversely, as data is received by the LAN9215, it is moved from the mac to the rx mil fifo, and then into the rx data fifo. when the rx data fifo fills up, data will continue to collect in the rx mil fifo. if the rx mil fifo fills up and overruns , subsequent rx frames will be lost until room is made in the rx data fifo. for each frame of data that is lost, the rx dropped frames counter (rx_drop) is incremented. rx and tx mil fifo levels are not visible to the host processor. rx and tx mil fifos operate independent of the tx data and rx data and status fifos. fifo levels set for the rx and tx data and status fifos do not take into consideration the mil fifos. 5.3.10 rx_dp_ctrl?receive datapath control register this register is used to discard unwanted receive frames. offset: 78h size: 32 bits bits description type default 31 rx data fifo fast forward (rx_ffwd): writing a ?1? to this bit causes the rx data fifo to fast-forward to t he start of the next frame. this bit will remain high until the rx data fifo fast-forward operation has completed. no reads should be issued to the rx data fifo while this bit is high. note: please refer to sect ion ?receive data fifo fast forward? on page 60 for detailed information regarding the use of rx_ffwd. r/w sc 0b 30-0 reserved ro -
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet revision 2.9 (03-01-12) 88 smsc LAN9215 datasheet 5.3.11 rx_fifo_inf?receive fifo information register this register contains the used space in the re ceive fifos of the LAN9215 ethernet controller. 5.3.12 tx_fifo_inf?transmit fifo information register this register contains the free space in the tr ansmit data fifo and the used space in the transmit status fifo in the LAN9215. offset: 7ch size: 32 bits bits description type default 31-24 reserved ro - 23-16 rx status fifo used space (rxsused). indicates the amount of space in dwords, used in the rx status fifo. ro 00h 15-0 rx data fifo used space (rxdused). ). reads the amount of space in bytes, used in the rx data fifo. for each receive frame, this field is incremented by the length of the receive data rounded up to the nearest dword (if the payload does not end on a dword boundary). ro 0000h offset: 80h size: 32 bits bits description type default 31-24 reserved ro - 23-16 tx status fifo used space (txsused). indicates the amount of space in dwords used in the tx status fifo. ro 00h 15-0 tx data fifo free space (tdfree). reads the amount of space in bytes, available in the tx data fifo. the appl ication should never write more data than is available, as indicated by this value. ro 1200h
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet smsc LAN9215 89 revision 2.9 (03-01-12) datasheet 5.3.13 pmt_ctrl? power mana gement control register this register controls the power management features. this register can be read while the LAN9215 is in a power saving mode. note: the LAN9215 must always be read at least once after power-up, reset, or upon return from a power-saving state or write operations will not function. offset: 84h size: 32 bits bits description type default 31:14 reserved ro - 13-12 power management mode (pm_mode) ? these bits set the LAN9215 into the appropriate power management mode. special care must be taken when modifying these bits. encoding : 00b ? d0 (normal operation) 01b ? d1 (wake-up frame and magic packet detection are enabled) 10b ? d2 (can perform energy detect) 11b ? reserved - do not set in this mode note: when the LAN9215 is in any of the reduced power modes, a write of any data to the byte_test regi ster will wake-up the device. do not perform writes to other addrresses while the ready bit in this register is cleared. sc 00b 11 reserved ro - 10 phy reset (phy_rst) ? writing a ?1? to this bit re sets the phy. the internal logic automatically holds the phy rese t for a minimum of 100us. when the phy is released from reset, th is bit is automatically cleared. all writes to this bit are ignored while this bit is high. sc 0b 9 wake-on-lan enable (wol_en) ? when set, the pme signal (if enabled with pme_en) will be asserted in accordance with the pme_ind bit upon a wol event. when set, the pme_int will also be asserted upon a wol event, regardless of the setting of the pme_en bit. r/w 0b 8 energy-detect enable (ed_en) - when set, the pme signal (if enabled with pme_en) will be asserted in accordance with the pme_ind bit upon an energy-detect event. when set, the pme_int will also be asserted upon an energy detect event, regardless of the setting of the pme_en bit. r/w 0b 7 reserved ro - 6 pme buffer type (pme_type) ? when cleared, enables pme to function as an open-drain buffer for use in a wi red-or configurati on. when set, the pme output is a push-pull driver. when configured as an open-drain output the pme_pol field is ignored, and the output is always active low. r/w nasr 0b
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet revision 2.9 (03-01-12) 90 smsc LAN9215 datasheet 5-4 wake-up status (wups) ? this field indicates the cause of a wake-up event detection as follows 00b -- no wake-up event detected 01b -- energy detected 10b -- wake-up frame or magic packet detected 11b -- indicates multiple events occurred wups bits are cleared by writing a ?1? to the appropriate bit. the device must return to the d0 state (ready bit set) before these bits can be cleared. note: in order to clear this bit, it is required that all event sources be cleared as well. the event sources are described in figure 3.10 pme and pme_int signal generationon page 43 . r/wc 00 3 pme indication (pme_ind). the pme signal can be configured as a pulsed output or a static signal, which is asserted upon detection of a wake-up event. when set, the pme signal will pulse acti ve for 50ms upon detection of a wake-up event. when clear, the pme signal is driven continuously upon detection of a wake- up event. the pme signal can be deactivated by clearing the wups bits, or by clearing the appropriate enable (refer to section 3.9.2.3, "power management event indicators," on page 43 ). r/w 0b 2 pme polarity (pme_pol). this bit controls the pola rity of the pme signal. when set, the pme output is an active high signal. when reset, it is active low. when pme is configured as an o pen-drain output this field is ignored, and the output is always active low. r/w nasr 0b 1 pme enable (pme_en). when set, this bit enables the external pme signal. this bit does not affect the pme interrupt (pme_int). r/w 0b 0 device ready (ready). when set, this bit indicates that LAN9215 is ready to be accessed. this register can be read when LAN9215 is in any power management mode. upon waking fr om any power management mode, including power-up, the host processor can interrogate this field as an indication when LAN9215 has stabilized and is fully alive. reads and writes of any other address are invalid until this bit is set. note: with the exception of hw_cfg and pmt_ctrl, read access to any internal resources is forbidden while the ready bit is cleared. ro - bits description type default
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet smsc LAN9215 91 revision 2.9 (03-01-12) datasheet 5.3.14 gpio_cfg?general purpos e io configuration register this register configures the gpio and led functions. offset: 88h size: 32 bits bits description type default 31 reserved ro - 30:28 led[3:1] enable (ledx_en). a ?1? sets the associated pin as an led output. when cleared low, the pin functions as a gpio signal. led1/gpio0 ? bit 28 led2/gpio1 ? bit 29 led3/gpio2 ? bit 30 r/w 000 27 reserved ro - 26:24 gpio interrupt polarity 0-2 (gpio_int_pol). when set high, a high logic level on the corresponding gpio pin will set the corresponding int_sts register bit. when cleared low, a lo w logic level on the corresponding gpio pin will set the corresponding int_sts register bit. gpio interrupts must also be enabled in gpiox_int_en in the int_en register. gpio0 ? bit 24 gpio1 ? bit 25 gpio2 ? bit 26 note: gpio inputs must be active for gr eater than 40ns to be recognized as interrupt inputs. r/w 000 23 reserved ro - 22:20 eeprom enable (eepr_en). the value of this field determines the function of the external eedio and eeclk: please refer to ta b l e 5 . 4 for the eeprom enable bit function definitions. note: the host must not change the f unction of the eedio and eeclk pins when an eeprom read or writ e cycle is in progress. do not use reserved settings. r/w 000 19 reserved ro - 18:16 gpio buffer type 0-2 (gpiobufn). when set, the output buffer for the corresponding gpio signal is conf igured as a push/pull driver. when cleared, the corresponding gpio set co nfigured as an open-drain driver. gpio0 ? bit 16 gpio1 ? bit 17 gpio2 ? bit 18 r/w 000 15:11 reserved ro - 10:8 gpio direction 0-2 (gpdirn). when set, enables the corresponding gpio as output. when cleared the gpio is enabled as an input. gpio0 ? bit 8 gpio1 ? bit 9 gpio2 ? bit 10 r/w 0000 7:5 reserved ro -
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet revision 2.9 (03-01-12) 92 smsc LAN9215 datasheet 5.3.15 gpt_cfg-general purpose timer configuration register this register configures the general purpose time r. the gp timer can be configured to generate host interrupts at intervals defined in this register. 4:3 gpo data 3-4 (gpodn). the value written is reflected on gpon. gpo3 ? bit 3 gpo4 ? bit 4 r/w 00 2:0 gpio data 0-2 (gpiodn) . when enabled as an output , the value written is reflected on gpion. when read, gpion reflects the current state of the corresponding gpio pin. gpio0 ? bit 0 gpio1 ? bit 1 gpio2 ? bit 2 r/w 000 table 5.4 eeprom enab le bit definitions [22] [21] [20] eedio f unction eeclk function 0 0 0 eedio eeclk 0 0 1 gpo3 gpo4 0 1 0 reserved 0 1 1 gpo3 rx_dv 1 0 0 reserved 1 0 1 tx_en gpo4 1 1 0 tx_en rx_dv 11 1 tx_clk rx_clk offset: 8ch size: 32 bits bits description type default 31-30 reserved ro - 29 gp timer enable (timer_en). when a one is written to this bit the gp timer is put into the run state. when cleared, the gp timer is halted. on the 1 to 0 transition of this bit the gpt_load field will be preset to ffffh. r/w 0 28-16 reserved ro - 15-0 general purpose timer pre-load (gpt_load). this value is pre-loaded into the gp-timer. r/w ffffh bits description type default
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet smsc LAN9215 93 revision 2.9 (03-01-12) datasheet 5.3.16 gpt_cnt-general purpose timer current count register this register reflects the cu rrent value of the gp timer. 5.3.17 word_swap?word swap control this register controls how words from the host data bus are mapped to the csrs and data fifos inside the LAN9215. the LAN9215 always sends data from the transmit data fifo to the network so that the low order word is sent fi rst, and always receives data fr om the network to the receive data fifo so that the low order word is received first. offset: 90h size: 32 bits bits description type default 31-16 reserved ro - 15-0 general purpose timer cu rrent count (gpt_cnt). this 16-bit field reflects the current value of the gp timer. ro ffffh offset: 98h size: 32 bits bits description type default 31:0 word swap. if this field is set to 00000000h, or anything except 0xffffffffh, the LAN9215 maps words with address bit a[1]=1 to the high order words of the csrs and data fifos, and words with address bit a[1]=0 to the low order words of the cs rs and data fifos. if this field is set to 0xffffffffh, the LAN9215 maps words with address bit a[1]=1 to the low order words of the csrs and data fifos, and words with address bit a[1]=0 to the high order wo rds of the csrs and data fifos. r/w nasr 00000000h
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet revision 2.9 (03-01-12) 94 smsc LAN9215 datasheet 5.3.18 free_run?free-run 25mhz counter this register reflects the value of the free-running 25mhz counter. 5.3.19 rx_drop? receiver dropped frames counter this register indicates the number of receive frames that have been dropped. offset: 9ch size: 32 bits bits description type default 31:0 free running sclk counter (fr_cnt): note: this field reflects the value of a free-running 32-bit counter. at reset the counter starts at zero and is incremented for every 25mhz cycle. when the maximum count has been reached the counter will rollover. since the bus interface is 16-bits wide, and this is a 32-bit counter, the count value is latched on the first read. the free_run counter can take up to 160ns to clear after a reset event. note: this counter will run regardless of the power management states d0, d1 or d2. ro - offset: a0h size: 32 bits bits description type default 31-0 rx dropped frame counter (rx_dfc). this counter is incremented every time a receive frame is dropped. rx_d fc is cleared on any read of this register. an interrupt can be issued when this counter passes through its halfway point (7fffffffh to 80000000h). rc 00000000h
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet smsc LAN9215 95 revision 2.9 (03-01-12) datasheet 5.3.20 mac_csr_cmd ? mac csr synchronizer command register this register is used to control the r ead and write operatio ns with the mac csr?s 5.3.21 mac_csr_data ? mac csr synchronizer data register this register is used in conjunction with th e mac_csr_cmd register to perform read and write operations with the mac csr?s offset: a4h size: 32 bits bits description type default 31 csr busy. when a 1 is written into this bit, the read or write operation is performed to the specified mac csr. this bit will remain set until the operation is complete. in the case of a read this means that the host can read valid data from the data register. the mac_csr_cmd and mac_csr_data registers should not be modified until this bit is cleared. sc 0 30 r/nw. when set, this bit indicates t hat the host is requesting a read operation. when clear, the host is performing a write. r/w 0 29-8 reserved. ro - 7-0 csr address. the 8-bit value in this field selects which mac csr will be accessed with the read or write operation. r/w 00h offset: a8h size: 32 bits bits description type default 31-0 mac csr data. value read from or written to the mac csr?s. r/w 00000000h
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet revision 2.9 (03-01-12) 96 smsc LAN9215 datasheet 5.3.22 afc_cfg ? automatic flow control configuration register this register configures the mechanism that controls both the automatic, and software-initiated transmission of pause frames and back pressure. note: the LAN9215 will not transmit pause frames or assert back pressure if the transmitter is disabled. offset: ach size: 32 bits bits description type default 31:24 reserved ro - 23:16 automatic flow control high level (afc_hi). specifies, in multiples of 64 bytes, the level at which flow control will trigger. when this limit is reached the chip will apply back pressure or will transmit a pause frame as programmed in bits [3:0] of this register. during full-duplex operation only a si ngle pause frame is transmitted when this level is reached. the pause ti me transmitted in this frame is programmed in the fcpt field of the flow register in the mac csr space. during half-duplex operation each incomi ng frame that matches the criteria in bits [3:0] of this register will be jammed for the period set in the back_dur field. r/w 00h 15:8 automatic flow control low level (afc_lo). specifies, in multiples of 64 bytes, the level at which a pause fr ame is transmitted with a pause time setting of zero. when the amount of data in the rx data fifo falls below this level the pause frame is transm itted. a pause time value of zero instructs the other transmitting device to immediately resume transmission. the zero time pause frame will only be transmitted if the rx data fifo had reached the afc_hi level and a pause frame was sent. a zero pause time frame is sent whenever automatic flow c ontrol in enabled in bits [3:0] of this register. note: when automatic flow control is enabled the afc_lo setting must always be less than the afc_hi setting. r/w 00h 7:4 backpressure duration (back_dur). when the LAN9215 automatically asserts back pressure, it will be asserted for this period of time. this field has no function and is not used in full-duplex mode. please refer to table 5.5 , describing backpressure duration bit mapping for more information. r/w 0h 3 flow control on multicast frame (fcmult). when this bit is set, the LAN9215 will assert back pressure when the afc level is reached and a multicast frame is received. this field has no function in full-duplex mode. r/w 0 2 flow control on broadcast frame (fcbrd). when this bit is set, the LAN9215 will assert back pressure when the afc level is reached and a broadcast frame is received. this field has no function in full-duplex mode. r/w 0 1 flow control on address decode (fcadd). when this bit is set, the LAN9215 will assert back pressure when the afc level is reached and a frame addressed to the LAN9215 is received. this field has no function in full-duplex mode. r/w 0
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet smsc LAN9215 97 revision 2.9 (03-01-12) datasheet 0 flow control on any frame (fcany). when this bit is set, the LAN9215 will assert back pressure, or transmit a pause frame when the afc level is reached and any frame is received. sett ing this bit enables full-duplex flow control when the LAN9215 is operating in full-duplex mode. when this mode is enabled during half-duplex operation, the flow controller does not decode the mac address and will send a pause frame upon receipt of a valid preamble (i.e., immediately at the beginning of the next frame after the rx data fifo level is reached). when this mode is enabled during full- duplex operation, the flow controller will immediately instruct the mac to send a pause frame when the rx data fifo level is reached. the mac will queue the pause frame transmission for the next available window. setting this bit overrides bits [3:1] of this register. r/w 0 table 5.5 backpressure duration bit mapping backpressure duration [19:16] 100mbs mode 10mbs mode 0h 5us 7.2us 1h 10us 12.2us 2h 15us 17.2us 3h 25us 27.2us 4h 50us 52.2us 5h 100us 102.2us 6h 150us 152.2us 7h 200us 202.2us 8h 250us 252.2us 9h 300us 302.2us ah 350us 352.2us bh 400us 402.2us ch 450us 452.2us dh 500us 502.2us eh 550us 552.2us fh 600us 602.2us bits description type default
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet revision 2.9 (03-01-12) 98 smsc LAN9215 datasheet 5.3.23 e2p_cmd ? eepr om command register this register is used to control the read and write operations with the serial eeprom. offset: b0h size: 32 bits bits description type default 31 epc busy: when a 1 is written into this bi t, the operation specified in the epc command field is performed at the specified eeprom address. this bit will remain set until the operation is complete. in the case of a read this means that the host can read valid data from the e2p data register. the e2p_cmd and e2p_data registers should not be modified until this bit is cleared. in the ca se where a write is attemp ted and an eeprom is not present, the epc busy remains busy until the epc time-out occurs. at that time the busy bit is cleared. note: epc busy will be high immediately following power-up or reset. after the eeprom controller has finished reading (or attempting to read) the mac address from the eeprom the epc busy bit is cleared. sc 0
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet smsc LAN9215 99 revision 2.9 (03-01-12) datasheet 30-28 epc command. this field is used to issue commands to the eeprom controller. the epc will execute commands when the epc busy bit is set. a new command must not be issued un til the previous command completes. this field is encoded as follows: read (read location): this command will cause a read of the eeprom location pointed to by epc address. t he result of the read is available in the e2p_data register. ewds (erase/write disable): after issued, the eeprom will ignore erase and write commands. to re-enable er ase/write operations issue the ewen command. ewen (erase/write enable): enables the eeprom for erase and write operations. the eeprom will allow eras e and write operations until the erase/write disable command is sent, or until power is cycled. note: the eeprom device will power-up in the erase/write-disabled state. any erase or write operati ons will fail until an erase/write enable command is issued. write (write location): if erase/write operations are enabled in the eeprom, this command will cause the contents of the e2p_data register to be written to the eeprom location selected by the epc address field. wral (write all): if erase/write operations are enabled in the eeprom, this command will cause the contents of the e2p_data register to be written to every eeprom memory location. erase (erase location): if erase/write operatio ns are enabled in the eeprom, this command will erase the location selected by the epc address field. eral (erase all): if erase/write operations are enabled in the eeprom, this command will initiate a bulk erase of the entire eeprom. reload (mac address reload): instructs the eeprom controller to reload the mac address from the eeprom. if a value of 0x a5 is not found in the first address of the eeprom, the eeprom is assumed to be un- programmed and mac address relo ad operation will fail. the ?mac address loaded? bit indicates a successful load of the mac address. r/w 0 27-10 reserved. ro - bits description type default [30] [29] [28] operation 0 0 0 read 001 ewds 0 1 0 ewen 011 write 100 wral 1 0 1 erase 1 1 0 eral 111 reload
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet revision 2.9 (03-01-12) 100 smsc LAN9215 datasheet 5.3.24 e2p_data ? eeprom data register this register is used in conjunction with the e2p_cmd register to perform read and write operations with the serial eeprom. 9 epc time-out. if an eeprom operation is per formed, and there is no response from the eeprom within 30ms, the eeprom controller will time- out and return to its idle state. this bit is set when a time-out occurs indicating that the last operation was unsuccessful. note: if the eedio signal pin is externally pulled-high, epc commands will not time out if the eeprom devic e is missing. in this case the epc busy bit will be cleared as soon as the command sequence is complete. it should also be noted that th e erase, eral, write and wral commands are the only epc commands that will time-out if an eeprom device is not present - and- the eedio signal is pulled low r/wc 0 8 mac address loaded. when set, this bit indicates that a valid eeprom was found, and that the mac ad dress programming has completed normally. this bit is set after a successful load of the mac address after power-up, or after a reload command has completed r/wc - 7-0 epc address. the 8-bit value in this field is used by the eeprom controller to address the specific me mory location in the serial eeprom. this is a byte aligned address. r/w 00h offset: b4h size: 32 bits bits description type default 31-8 reserved ro - 7:0 eeprom data. value read from or written to the eeprom. r/w 00h bits description type default
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet smsc LAN9215 101 revision 2.9 (03-01-12) datasheet 5.4 mac control and status registers these registers are located in the mac module and are accessed indirectly through the mac-csr synchronizer port. table 5.6, "mac csr register map" , shown below, lists the mac registers that are accessible through the indexing method using the mac_csr_cmd and mac_csr_data registers (see sections mac_csr_cmd ? mac csr synchr onizer command register and mac_csr_data ? mac csr synchronizer data register). table 5.6 mac csr register map mac control and status registers index symbol register name default 1mac_cr mac control register 00040000h 2 addrh mac address high 0000ffffh 3 addrl mac address low ffffffffh 4 hashh multicast hash table high 00000000h 5 hashl multicast hash table low 00000000h 6mii_acc mii access 00000000h 7 mii_data mii data 00000000h 8flow flow control 00000000h 9vlan1 vlan1 tag 00000000h avlan2 vlan2 tag 00000000h bwuff wake-up frame filter 00000000h cwucsr wake-up control and status 00000000h
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet revision 2.9 (03-01-12) 102 smsc LAN9215 datasheet 5.4.1 mac_cr?mac control register this register establishes the rx and tx operation modes and controls for address filtering and packet filtering. offset: 1 attribute: r/w default value: 00040000h size: 32 bits bits description 31 receive all mode (rxall). when set, all incoming packets will be received and passed on to the address filtering function for processing of the sele cted filtering mode on the received frame. address filtering then occurs and is reported in receive stat us. when reset, only frames that pass destination address filtering will be sent to the application. 30-24 reserved 23 disable receive own (rcvown). when set, the mac disables the reception of frames when the mii tx_en signal is asserted. the mac blocks the tr ansmitted frame on the receive path. when reset, the mac receives all packets the phy gives, including those transmitted by the mac.this bit should be reset when the full duplex mode bit is set. 22 reserved 21 loopback operation mode (loopbk). selects the loop back operation modes for the mac. this is only for full duplex mode 1?b0: normal: no feedback 1?b1: internal: through mii in internal loopback mode, the tx frame is received by the internal mii interface, and sent back to the mac without being sent to the phy. note: when enabling or disabling the loopback mode it can take up to 10 s for the mode change to occur. the transmitter and receiver must be stopped and disabled when modifying the loopbk bit. the transmit ter or receiver should not be enabled within10 s of modifying the loopbk bit. 20 full duplex mode (fdpx). when set, the mac operates in full-du plex mode, in which it can transmit and receive simultaneously. in full-duplex mode, th e heartbeat check is disa bled and the heartbeat fail status should thus be ignored. 19 pass all multicast (mcpas). when set, indicates that all incoming frames with a multicast destination address (first bit in the destination address field is 1) are received. incoming frames with physical address (individual address/unicast) destinations are filtered and rece ived only if the address matches the mac address. 18 promiscuous mode (prms). when set, indicates that any incoming frame is received regardless of its destination address. 17 inverse filtering (invfilt). when set, the address check function operates in inverse filtering mode. this is valid only during perfect filtering mode. 16 pass bad frames (passbad). when set, all incoming frames that passed address filtering are received, including runt frames and collided frames. 15 hash only filtering mode (ho). when set, the address check functi on operates in the imperfect address filtering mode both fo r physical and multicast addresses 14 reserved
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet smsc LAN9215 103 revision 2.9 (03-01-12) datasheet 13 hash/perfect filtering mode (hpfilt). when reset (0), the lan 9215 will implement a perfect address filter on incoming frames according the address specified in the mac address register. when set (1), the address check function does im perfect address filtering of multicast incoming frames according to the hash table specified in the multicast hash table register. if the hash only filtering mode (ho) bit is set (1), then the physical (ia) are im perfect filtered too. if the hash only filtering mode (ho) bit is reset (0), then the ia addresses are perfect address filtered according to the mac address register 12 late collision control (lcoll). when set, enables retransmission of the collided frame even after the collision period (late collision). when reset, the mac disables frame transmission on a late collision. in any case, the late collision status is appropriately updated in the transmit packet status. 11 disable broadcast frames (bcast). when set, disables the rec eption of broadcast frames. when reset, forwards all broadcast frames to the application. note: when wake-up frame detection is en abled via the wuen bit of the wucsr?wake-up control and status register , a broadcast wake-up frame will wake-up the device despite the state of this bit. 10 disable retry (disrty). when set, the mac attempts only one transmission. when a collision is seen on the bus, the mac ignores the current frame and goes to the next frame and a retry error is reported in the transmit status. when reset, the mac attempts 16 transmissions before signaling a retry error. 9 reserved 8 automatic pad stripping (padstr). when set, the mac strips the pad field on all incoming frames, if the length field is less than 46 bytes. the fcs fi eld is also stripped, since it is computed at the transmitting station based on the data and pad fiel d characters, and is invalid for a received frame that has had the pad characters stripped. receive frames with a 46-byte or greater length field are passed to the application unmodified (fcs is not st ripped). when reset, the mac passes all incoming frames to the host unmodified. bits description
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet revision 2.9 (03-01-12) 104 smsc LAN9215 datasheet 7-6 backoff limit (bolmt). the bolmt bits allow the user to set its back-off limit in a relaxed or aggressive mode. accordi ng to ieee 802.3, the mac has to wait for a random number [r] of slot- times** after it detects a collision, where: (eq.1)0 < r < 2 k the exponent k is dependent on how many times the cu rrent frame to be transmitted has been retried, as follows: (eq.2)k = min (n, 10) where n is the current number of retries. if a frame has been retried three times, then k = 3 an d r= 8 slot-times maximum. if it has been retried 12 times, then k = 10, and r = 1024 slot-times maximum. an lfsr (linear feedback shift register) 20-bit co unter emulates a 20bit random number generator, from which r is obtained. once a collision is detect ed, the number of the curr ent retry of the current frame is used to obtain k (eq.2). this value of k tr anslates into the number of bits to use from the lfsr counter. if the value of k is 3, the mac takes the value in the first three bits of the lfsr counter and uses it to count down to zero on every slot-tim e. this effectively causes the mac to wait eight slot-times. to give the user more flexibility, the bolmt value forces the number of bits to be used from the lfsr counter to a predetermined value as in the table below. thus, if the value of k = 10, the mac will look at the bolmt if it is 00, then use the lower ten bits of the lfsr counter for the wait countdown. if the bolmt is 10, then it will only use the value in the first four bits for the wait countdown, etc. **slot-time = 512 bit times. (see ieee 802 .3 spec., secs. 4. 2.3.25 and 4.4.2.1) 5 deferral check (dfchk). when set, enables the deferral check in the mac. the mac will abort the transmission attempt if it has def erred for more than 24,288 bit times. deferral starts when the transmitter is ready to transmit, but is prevented fr om doing so because the crs is active. defer time is not cumulative. if the transmitter defers for 10,000 bit times, then transmit s, collides, backs off, and then has to defer again after completion of back-off, the deferral timer resets to 0 and restarts. when reset, the deferral check is disabled in the mac and the mac defers indefinitely. 4 reserved 3 transmitter enable (txen). when set, the mac?s transmitter is enabled and it will transmit frames from the buffer onto the cable. when reset, the mac?s transmitter is disabled and will not transmit any frames. 2 receiver enable (rxen). when set (1), the mac?s receiver is enabled and will receive frames from the internal phy. when reset, the mac?s receiver is disabled and will not receive any frames from the internal phy. 1-0 reserved bits description bolmt value # bits used from lfsr counter 2?b00 10 2?b01 8 2?b10 4 2?b11 1
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet smsc LAN9215 105 revision 2.9 (03-01-12) datasheet 5.4.2 addrh?mac a ddress high register the mac address high register contains the upper 16-bits of the physical address of the mac. the contents of this register ar e optionally loaded from the eeprom at power-on through the eeprom controller if a programmed eeprom is detected. the least si gnificant byte of this register (bits [7:0]) is loaded from address 0x05 of the eeprom. the seco nd byte (bits [15:8]) is loaded from address 0x06 of the eeprom. please refer to section 4.6 for more information on the eeprom. section 5.4.3 details the byte ordering of the addrl and addrh r egisters with respect to the reception of the ethernet physical address. offset: 2 attribute: r/w default value: 0000ffffh size: 32 bits bits description 31-16 reserved 15-0 physical address [47:32]. this field contains the upper 16-bit s (47:32) of the physical address of the LAN9215 device. the content of this field is undefined until loaded from the eeprom at power- on. the host can update the contents of this fiel d after the initialization process has completed.
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet revision 2.9 (03-01-12) 106 smsc LAN9215 datasheet 5.4.3 addrl?mac addr ess low register the mac address low register contains the lower 32 bits of the physical address of the mac. the contents of this register ar e optionally loaded from the eeprom at power-on through the eeprom controller if a programmed eeprom is detected. the least si gnificant byte of this register (bits [7:0]) is loaded from address 0x01 of the eeprom. the most significant byte of this register is loaded from address 0x04 of the eeprom. please refer to section 4.6 for more information on the eeprom. table 5.7 below illustrates the byte ordering of the addrl and addrh registers with respect to the reception of the ethernet physical address. also shown is the correlation between the eeprom addresses and addrl and addrh registers. as an example, if the desired ethernet physical address is 12-34-56-78-9a-bc, the addrl and addrh registers would be programmed as shown in figure 5.2 . the values required to automatically load this configuration from the eeprom are also shown. figure 5.2 example addrl, addrh and eeprom setup offset: 3 attribute: r/w default value: ffffffffh size: 32 bits bits description 31-0 physical address [31:0]. this field contains the lower 32 bits (31:0) of the physical address of the LAN9215 device. the content of this field is un defined until loaded from the eeprom at power-on. the host can update the contents of this field after the initialization process has completed. table 5.7 addrl, addrh and eeprom byte ordering eeprom address addrn order of reception on ethernet 0x01 addrl[7:0] 1 st 0x02 addrl[15:8] 2 nd 0x03 addrl[23:16] 3 rd 0x04 addrl[31:24] 4 th 0x05 addrh[7:0] 5 th 0x06 addrh[15:8] 6 th 0x12 0 7 0x34 8 15 0x56 16 23 0x78 24 31 addrl 0x9a 0 7 0xbc 8 15 addrh xx 16 23 xx 24 31 0xa5 0x12 0x34 0x56 0x78 0x9a 0xbc 0x00 0x01 0x02 0x03 0x04 0x05 0x06 eeprom
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet smsc LAN9215 107 revision 2.9 (03-01-12) datasheet note: by convention, the left most by te of the ethernet address (in this example 0x12) is the most significant byte and is transmitted/received first. 5.4.4 hashh?multicast h ash table high register the 64-bit multicast table is used for group address fi ltering. for hash filtering, the contents of the destination address in the incoming frame is used to index the contents of the hash table. the most significant bit determines the register to be used (h i/low), while the other five bits determine the bit within the register. a value of 00000 selects bit 0 of the multicast hash table lo register and a value of 11111 selects the bit 31 of the multicast hash table hi register. if the corresponding bit is 1, then the multicast frame is accepted. otherwise, it is rejected. if the ?pass all multicast? (mcpas) bit is set (1), then all multicast frames are accepted regardless of the multicast hash values. the multicast hash table hi register contains the higher 32 bits of the hash table and the multicast hash table low register contains the lower 32 bits of the hash table. 5.4.5 hashl?multicast h ash table low register this register defines the lower 32-bits of the multicast hash table. please refer to table 5.4.4, "hashh?multicast hash table high register" for further details. offset: 4 attribute: r/w default value: 00000000h size: 32 bits bits description 31-0 upper 32 bits of the 64-bit hash table offset: 5 attribute: r/w default value: 00000000h size: 32 bits bits description 31-0 lower 32 bits of the 64-bit hash table
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet revision 2.9 (03-01-12) 108 smsc LAN9215 datasheet 5.4.6 mii_acc?mii access register this register is used to contro l the management cycles to the phy. 5.4.7 mii_data?mii data register this register contains either the data to be written to the phy register specified in the mii access register, or the read data from the phy register whose index is specified in the mii access register. offset: 6 attribute: r/w default value: 00000000h size: 32 bits bits description 31-16 reserved 15-11 phy address: selects the external or internal phy based on its address. the internal phy is set to address 00001b. 10-6 mii register index (miirinda): these bits select the desired mii register in the phy. 5-2 reserved 1 mii write (miiwnr): setting this bit tells the phy that this will be a write operation using the mii data register. if this bit is not set, this will be a read operation, packing the data in the mii data register. 0 mii busy (miibzy): this bit must be polled to determine when the mii register access is complete. this bit must read a logical 0 before writing to this register and mii data register. the lan driver software must set (1 ) this bit in order for the LAN9215 to read or write any of the mii phy registers. during a mii register acce ss, this bit will be set, signifying a read or write access is in progress. the mii data register must be kept valid until the mac clears this bit during a phy write operation. the mii data register is invalid until the mac has cleared this bit during a phy read operation. offset: 7 attribute: r/w default value: 00000000h size: 32 bits bits description 31-16 reserved 15-0 mii data. this contains the 16-bit value read from the phy read operation or the 16-bit data value to be written to the phy before an mii write operation.
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet smsc LAN9215 109 revision 2.9 (03-01-12) datasheet 5.4.8 flow?flow control register this register controls the generation and receptio n of the control (pause command) frames by the mac?s flow control block. the control frame fields ar e selected as specified in the 802.3x specification and the pause-time value from this register is used in the ?pause time? field of the control frame. in full-duplex mode the fcbsy bi t is set until the control frame is tr ansferred onto the cable. in half- duplex mode fcbsy is set while back pressure is being asserted. the ho st has to make sure that the busy bit is cleared before writin g the register. the pass control frame bit (fcpass) does not affect the sending of the frames, including control frames, to the application interface. the flow control enable (fcen) bit enables the receive portion of the flow control block. this register is used in conjunction with the afc_ cfg register in the slave csrs to configure flow control. software flow control is initiated using the afc_cfg register. note: the LAN9215 will not transmit pause frames or assert back pressure if the transmitter is disabled. offset: 8 attribute: r/w default value: 00000000h size: 32 bits bits description 31-16 pause time (fcpt). this field indicates the value to be used in the pause time field in the control frame. this field must be initialized before full-duplex automatic flow control is enabled. 15-3 reserved 2 pass control frames (fcpass). when set, the mac will pass the pause frame to the host. the application must accept or discard a received fram e based on the packet filter control bit. the mac receives, decodes and performs the pause functi on when a valid pause frame is received in full- duplex mode and when flow control is enabled (fce bit set). when reset, the mac resets the packet filter bit in the receive packet status. the mac always passes the data of all frames it receives (including flow control frames) to the application. frames that do not pass address filtering, as well as fr ames with errors, are passed to the application. the application must discard or retain the received frame?s data based on the received frame?s status field. filtering modes (promiscuous mode, for example) take precedence over the fcpass bit. 1 flow control enable (fcen). when set, enables the mac flow control function. the mac decodes all incoming frames for control frames; if it re ceives a valid control frame (pause command), it disables the transmitter for a specified time (decoded pause time x slot time). when reset, the mac flow control function is disabled; the mac does not decode frames for control frames. note: flow control is applicable when the mac is se t in full duplex mode. in half-duplex mode, this bit enables the backpressure function to cont rol the flow of received frames to the mac. 0 flow control busy (fcbsy). this bit is set high whenever a pause frame or back pressure is being transmitted. this bit should read logical 0 before writing to the flow control (flow) register. during a transfer of control frame, this bit continues to be set, signifying that a frame transmission is in progress. after the pause control frame?s transm ission is complete, th e mac resets to 0. notes: ? when writing this register th e fcbsy bit must always be zero. ? applications must always write a zero to this bit
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet revision 2.9 (03-01-12) 110 smsc LAN9215 datasheet 5.4.9 vlan1?vlan1 tag register this register contains the vlan tag field to iden tify vlan1 frames. for vlan frames the legal frame length is increased from 1518 bytes to 1522 bytes. 5.4.10 vlan2?vlan2 tag register this register contains the vlan tag field to iden tify vlan2 frames. for vlan frames the legal frame length is increased from 1518 bytes to 1522 bytes. offset: 9 attribute: r/w default value: 00000000h size: 32 bits bits description 31-16 reserved 15-0 vlan1 tag identifier (vti1). this contains the vlan tag field to identify the vlan1 frames. this field is compared with the 13th and 14th bytes of the incoming frames for vlan1 frame detection. if used, this register must be set to 0x8100. offset: a attribute: r/w default value: 00000000h size: 32 bits bits description 31-16 reserved 15-0 vlan2 tag identifier (vti2). this contains the vlan tag field to identify the vlan2 frames. this field is compared with the 13th and 14th bytes of the incoming frames for vlan2 frame detection.if used, this register must be set to 0x8100.
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet smsc LAN9215 111 revision 2.9 (03-01-12) datasheet 5.4.11 wuff?wake-up frame filter this register is used to conf igure the wake up frame filter. 5.4.12 wucsr?wake-up control and status register this register contains data pertaining to the mac?s remote wake-up status and capabilities. offset: b attribute: wo default value: 00000000h size: 32 bits bits description 31-0 wake-up frame filter (wff). wake-up frame filter (wff). the wa ke-up frame filter is configured through this register using an indexing mechanism. af ter power-on reset, hardware reset, or soft reset, the mac loads the first value written to this locati on to the first dword in the wake-up frame filter (filter 0 byte mask). the second value written to this location is loaded to the second dword in the wake-up frame filter (filter 1 byte mask) and so on. once all eight dwords have been written, the internal pointer will once again point to the first entry and the filter entries can be modified in the same manner. note: this is a write-only register. offset: c attribute: r/w default value: 00000000h size: 32 bits bits description 31-10 reserved 9 global unicast enable (gue). when set, the mac wakes up from power-saving mode on receipt of a global unicast frame. a global unicast frame has the mac address [0] bit set to 0. 8-7 reserved 6 remote wake-up frame received (wufr). the mac, upon receiving a valid remote wake-up frame, sets this bit. 5 magic packet received (mpr). the mac, upon receiving a valid magic packet, sets this bit. 4-3 reserved 2 wake-up frame enabled (wuen). when set, remote wake-up mode is enabled and the mac is capable of detecting wake-up frames as programmed in the wa ke-up frame filter. 1 magic packet enable (mpen). when set, magic packet wake-up mode is enabled. 0 reserved
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet revision 2.9 (03-01-12) 112 smsc LAN9215 datasheet 5.5 phy registers the phy registers are not memory mapped. these registers are acce ssed indirectly through the mac via the mii_acc and mii_data registers. an index must be used to access individual phy registers. phy register indexes are shown in table 5.8, "LAN9215 phy control and status register" . note: the nasr ( not affected by software reset) designation is only applicable when bit 15 of the phy basic control re gister (reset) is set. table 5.8 LAN9215 phy control and status register phy control and status registers index (in decimal) register name 0 basic control register 1 basic status register 2 phy identifier 1 3 phy identifier 2 4 auto-negotiation advertisement register 5 auto-negotiation link partner ability register 6 auto-negotiation expansion register 17 mode control/status register 18 special modes register 27 special control/status indications 29 interrupt source register 30 interrupt mask register 31 phy special control/ status register
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet smsc LAN9215 113 revision 2.9 (03-01-12) datasheet 5.5.1 basic control register note 5.1 the default value of this bit is dete rmined by pin 74 "speed_sel ". please refer to the pin description section for more details index (in decimal): 0 size: 16-bits bits description type default 15 reset. 1 = software reset. bit is self-clearing. for best results, when setting this bit do not set other bits in this register. rw/sc 0 14 loopback. 1 = loopback mode, 0 = normal operation rw 0 13 speed select. 1 = 100mbps, 0 = 10mbps. ignored if auto negotiation is enabled (0.12 = 1). rw see note 5.1 12 auto-negotiation enable. 1 = enable auto-negotiate process (overrides 0.13 and 0.8) 0 = disable auto-negotiate process. rw see note 5.1 11 power down. 1 = general power down-mode, 0 = normal operation. note: after this bit is cleared, the phy may auto-negotiate with it's partner station. this process may take a few seconds to complete. once auto-negotiation is complete, bit 5 of the phy's basic status register will be set. rw 0 10 reserved ro 0 9 restart auto-negotiate. 1 = restart auto-negotiate process 0 = normal operation. bit is self-clearing. rw/sc 0 8 duplex mode. 1 = full duplex, 0 = half duplex . ignored if auto negotiation is enabled (0.12 = 1). rw 0 7 collision test. 1 = enable col test, 0 = disable col test rw 0 6-0 reserved ro 0
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet revision 2.9 (03-01-12) 114 smsc LAN9215 datasheet 5.5.2 basic status register 5.5.3 phy identifier 1 index (in decimal): 1 size: 16-bits bits description type default 15 100base-t4. 1 = t4 able, 0 = no t4 ability ro 0 14 100base-tx full duplex. 1 = tx with full duplex, 0 = no tx full duplex ability. ro 1 13 100base-tx half duplex. 1 = tx with half duplex, 0 = no tx half duplex ability. ro 1 12 10base-t full duplex. 1 = 10mbps with full duplex 0 = no 10mbps with full duplex ability ro 1 11 10base-t half duplex. 1 = 10mbps with half duplex 0 = no 10mbps with half duplex ability ro 1 10-6 reserved ro 0 5 auto-negotiate complete. 1 = auto-negotiate process completed 0 = auto- negotiate process not completed ro 0 4 remote fault. 1 = remote fault condition detected 0 = no remote fault ro/lh 0 3 auto-negotiate ability. 1 = able to perform auto-negotiation function 0 = unable to perform auto-negotiation function ro 1 2 link status. 1 = link is up, 0 = link is down ro/ll 0 1 jabber detect. 1 = jabber condition det ected 0 = no jabber condition detected ro/lh 0 0 extended capabilities. 1 = supports extended capabilities registers 0 = does not support extended capabilities registers. ro 1 index (in decimal): 2 size: 16-bits bits description type default 15-0 phy id number. assigned to the 3rd through 18th bits of the organizationally unique identifier (oui), respectively. ro 0x0007h
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet smsc LAN9215 115 revision 2.9 (03-01-12) datasheet 5.5.4 phy identifier 2 5.5.5 auto-negotiation advertisement note 5.2 when both symmetric pause and asymmetric pause support are advertised (value of 11), the device will only be configured to, at most, one of the two settings upon auto- negotiation completion. index (in decimal): 3 size: 16-bits bits description type default 15-10 phy id number assigned to the 19th through 24th bits of the oui. ro 0xc0c3h 9 - 4 model number. six-bit manufacturer?s model number. ro 3 - 0 revision number. four-bit manufacturer?s revision number. ro index (in decimal): 4 size: 16-bits bits description type default 15:14 reserved ro 00 13 remote fault. 1 = remote fault detected, 0 = no remote fault r/w 0 12 reserved r/w 0 11:10 pause operation. (see note 5.2 ) 00 no pause 01 symmetric pause 10 asymmetric pause 11 advertise support for both symmetric pause and asymmetric pause r/w 00 9 reserved ro 0 8 100base-tx full duplex. 1 = tx with full duplex, 0 = no tx full duplex ability r/w see note 5.3 7 100base-tx. 1 = tx able, 0 = no tx ability r/w 1 6 10base-t full duplex. 1 = 10mbps with full duplex 0 = no 10mbps with full duplex ability r/w see note 5.3 5 10base-t. 1 = 10mbps able, 0 = no 10mbps ability r/w see note 5.3 4:0 selector field. [00001] = ieee 802.3 r/w 00001
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet revision 2.9 (03-01-12) 116 smsc LAN9215 datasheet note 5.3 this default value of this bit is determine d by pin 74 "speed_sel". please refer to the pin description section for more details. 5.5.6 auto-negotiation link partner ability index (in decimal): 5 size: 16-bits bits description type default 15 next page. 1 = next page capable, 0 = no next page ability. this device does not support next page ability. ro 0 14 acknowledge. 1 = link code word received from partner 0 = link code word not yet received note: this bit will always read 0 ro 0 13 remote fault. 1 = remote fault detected, 0 = no remote fault ro 0 12 reserved ro 0 11-10 pause operation . 00 no pause supported by partner station 01 symmetric pause supported by partner station 10 asymmetric pause supported by partner station 11 both symmetric pause and asymme tric pause supported by partner station ro 00 9 100base-t4. 1 = t4 able, 0 = no t4 ability ro 0 8 100base-tx full duplex. 1 = tx with full duplex, 0 = no tx full duplex ability ro 0 7 100base-tx. 1 = tx able, 0 = no tx ability ro 0 6 10base-t full duplex. 1 = 10mbps with full duplex 0 = no 10mbps with full duplex ability ro 0 5 10base-t. 1 = 10mbps able, 0 = no 10mbps ability ro 0 4:0 selector field. [00001] = ieee 802.3 ro 00001
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet smsc LAN9215 117 revision 2.9 (03-01-12) datasheet 5.5.7 auto-negotiation expansion 5.5.8 mode control/status note 5.4 the default value of this bit will vary depe ndant on the current link state of the line. index (in decimal): 6 size: 16-bits bits description type default 15:5 reserved ro 0 4 parallel detection fault. 1 = fault detected by parallel detection logic 0 = no fault detected by parallel detection logic ro/lh 0 3 link partner next page able. 1 = link partner has next page ability 0 = link partner does not have next page ability ro 0 2 next page able. 1 = local device has next page ability 0 = local device does not have next page ability ro 0 1 page received. 1 = new page received 0 = new page not yet received ro/lh 0 0 link partner auto-negotiation able. 1 = link partner has auto-negotiation ability 0 = link partner does not have auto-negotiation ability ro 0 index (in decimal): 17 size: 16-bits bits description type default 15-14 reserved. write as 0; ignore on read. rw 0 13 edpwrdown. enable the energy detect power-down mode: 0=energy detect power-down is disabled 1=energy detect power-down is enabled rw 0 12-2 reserved. write as 0, ignore on read rw 0 1 energyon. indicates whether energy is detec ted. this bit goes to a ?0? if no valid energy is detected within 256ms. reset to ?1? by hardware reset, unaffected by sw reset. ro see note 5.4 0 reserved. write as ?0?. ignore on read. rw 0
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet revision 2.9 (03-01-12) 118 smsc LAN9215 datasheet 5.5.9 special modes note 5.5 when mode=111, the register 0 bits 13 and 8 are variable dependant on the auto- negotiated speed and duplex. index (in decimal): 18 size: 16-bits address description type default 15-8 reserved rw, nasr 7:5 mode: phy mode of operation. refer to table 5.9 for more details. rw, nasr see table 5.9 4:0 phyad: phy address: the phy address is used for the smi address. rw, nasr 00001b table 5.9 mode control mode mode definitions default register bit values register 0 register 4 [13,12,10,8] [8,7,6,5] 000 10base-t half duplex. auto-negotiation disabled. 0000 n/a 001 10base-t full duplex. auto-negotiation disabled. 0001 n/a 010 100base-tx half duplex. auto-negotiation disabled. crs is active during transmit & receive. 1000 n/a 011 100base-tx full duplex. auto-negotiation disabled. crs is active during receive. 1001 n/a 100 100ase-tx half duplex is advertised. auto- negotiation enabled. crs is active during transmit & receive. 1100 0100 101 repeater mode. auto -negotiation enabled. 100base-tx half duplex is advertised. crs is active during receive. 1100 0100 110 reserved - do not set the LAN9215 in this mode. n/a n/a 111 all capable. auto-negotiation enabled. x10x note 5.5 1111
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet smsc LAN9215 119 revision 2.9 (03-01-12) datasheet 5.5.10 special control/status indications index (in decimal): 27 size: 16-bits address description mode default 15 override amdix strap 0 - amdix_en (pin 73) enables or disables hp auto mdix 1 - override pin 73. phy register 27.14 and 27.13 determine mdix function rw 0 14 auto-mdix enable: only effective when 27. 15=1, otherwise ignored. 0 = disable auto-mdix. 27.13 determines normal or reversed connection. 1 = enable auto-mdix. 27.13 must be set to 0. rw 0 13 auto-mdix state. only effective when 27. 15=1, otherwise ignored. when 27.14 = 0 (manually set mdix state): 0 = no crossover (tpo = output, tpi = input) 1 = crossover (tpo = input, tpi = output) when 27.14 = 1 (automatic mdix ) this bit must be set to 0. do not use the combination 27.15=1, 27.14=1, 27.13=1. rw 0 12:11 reserved: write as 0. ignore on read. rw 0 10 vcooff_lp: forces the receive pll 10m to lock on the reference clock at all times: 0 - receive pll 10m can lock on reference or line as needed (normal operation) 1 - receive pll 10m is locked on the reference clock. in this mode 10m data packets cannot be received. rw, nasr 0 9-5 reserved: write as 0. ignore on read. rw 0 4 xpol: polarity state of the 10base-t: 0 - normal polarity 1 - reversed polarity ro 0 3:0 reserved: read only - writing to these bits have no effect. ro xxxxb
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet revision 2.9 (03-01-12) 120 smsc LAN9215 datasheet 5.5.11 interrupt source flag note 5.6 the default value of this bit will vary depe ndant on the current link state of the line. 5.5.12 interrupt mask index (in decimal): 29 size: 16-bits bits description type default 15-8 reserved. ignore on read. ro/lh 0 7 int7. 1= energyon generated, 0= not source of interrupt ro/lh 0 6 int6. 1= auto-negotiation complete, 0= not source of interrupt ro/lh 0 5 int5. 1= remote fault detected, 0= not source of interrupt ro/lh 0 4 int4. 1= link down (link status negated), 0= not source of interrupt ro/lh see note 5.6 3 int3. 1= auto-negotiation lp acknowled ge, 0= not source of interrupt ro/lh 0 2 int2. 1= parallel detection fault, 0= not source of interrupt ro/lh 0 1 int1. 1= auto-negotiation page received, 0= not source of interrupt ro/lh 0 0 reserved. ro/lh 0 index (in decimal): 30 size: 16-bits bits description type default 15-8 reserved. write as 0; ignore on read. ro 0 7-0 mask bits. 1 = interrupt source is enabled 0 = interrupt source is masked rw 0
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet smsc LAN9215 121 revision 2.9 (03-01-12) datasheet 5.5.13 phy special control/status note 5.7 see table 2.2, ?default ethernet settings,? on page 17 , for default settings. index (in decimal): 31 size: 16-bits bits description type default 15 - 13 reserved ro 000b 12 autodone. auto-negotiation done indication: 0 = auto-negotiation is not done or disabled (or not active) 1 = auto-negotiation is done ro 0b 11-5 reserved. write as 0000010b, ignore on read. rw 0000010b 4-2 speed indication. hcdspeed value: [001]=10mbps half-duplex [101]=10mbps full-duplex [010]=100base-tx half-duplex [110]=100base-tx full-duplex ro see note 5.7 1-0 reserved. write as 0; ignore on read ro 00b
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet revision 2.9 (03-01-12) 122 smsc LAN9215 datasheet chapter 6 timing diagrams 6.1 host interface timing the LAN9215 supports the following host cycles: read cycles: ? pio reads (ncs or nrd controlled) ? pio burst reads (ncs or nrd controlled) ? rx data fifo direct pio re ads (ncs or nrd controlled) ? rx data fifo direct pio burst reads (ncs or nrd controlled) write cycles: ? pio writes (ncs and nwr controlled) ? tx data fifo direct pio wr ites (ncs or nwr controlled) all timing measurements were verified under the following conditions: temperature: ................................................................................................................... .....0 o c to +70 o c device vdd:.................................................................................................................... +3.30 v +/- 10% load capacitance: .............................................................................................................. .............. 25pf 6.1.1 special restrictions on back-to-back write/read cycles it is important to note that there are specific re strictions on the timing of back-to-bac k write-read operations. these restrictions c oncern reading the control regist ers after any write cycle to the LAN9215 device. in many cases there is a requir ed minimum delay between writing to the LAN9215, and the subsequent side effect (change in the control register value). for example, when writing to the tx data fifo, it takes up to 165ns for the level indication to change in the tx_fifo_inf register. in order to prevent the host from reading stale data after a write operation, minimum wait periods must be enforced. these periods are specified in table 6.1, "read after write timing rules" . the host processor is required to wait the specified period of time after any write to the LAN9215 before reading the resource specified in the table. these wait periods are for read operations that immediately follow any write cycle. note that the requ ired wait period is dependant upon the register being read after the write. performing "dummy" reads of the byte_test register is a c onvenient way to guarantee that the minimum write-to-read timi ng restriction is met. table 6.1 also shows the number of dummy reads that are required before reading the register indicat ed. the number of byte_test reads in this table is based on the minimum timing for t cycle (165ns). for microprocessors with slower busses the number of reads may be reduced as long as the total time is equal to, or greater than the time specified in the table. note that dummy reads of the byte_test register are not required as long as the minimum time period is met.
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet smsc LAN9215 123 revision 2.9 (03-01-12) datasheet table 6.1 read after write timing rules register name minimum wait time for read following any write cycle (in ns) number of byte_test reads (assuming t cycle of 165ns) id_rev 0 0 irq_cfg 165 1 int_sts 165 1 int_en 165 1 byte_test 0 0 fifo_int 165 1 rx_cfg 165 1 tx_cfg 165 1 hw_cfg 165 1 rx_dp_ctrl 165 1 rx_fifo_inf 0 0 tx_fifo_inf 165 1 pmt_ctrl 330 2 gpio_cfg 165 1 gpt_cfg 165 1 gpt_cnt 165 1 word_swap 165 1 free_run 330 2 rx_drop 0 0 mac_csr_cmd 165 1 mac_csr_data 165 1 afc_cfg 165 1 e2p_cmd 165 1 e2p_data 165 1
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet revision 2.9 (03-01-12) 124 smsc LAN9215 datasheet 6.1.2 special restrictions on back-to-back read cycles there are also restrictions on specific back-to -back read operations. thes e restrictions concern reading specific registers after readi ng resources that have side effects. in many cases there is a delay between reading the LAN9215, and the subsequent i ndication of the expected change in the control register values. in order to prevent the host from reading stale data on back-to-back reads, minimum wait periods have been established. these periods are specified in table 6.2, "read after read timing rules" . the host processor is required to wait the specified period of time between read operations of specific combinations of resources. the wait period is dep endant upon the combination of registers being read. performing "dummy" reads of the byte_test register is a c onvenient way to guarantee that the minimum wait time restriction is met. table 6.2 also shows the number of dummy reads that are required for back-to-back read operations. the number of byte_test reads in this table is based on the minimum timing for tcycle (165ns). for micropro cessors with slower busses the number of reads may be reduced as long as the total time is equal to , or greater than the time specified in the table. dummy reads of the byte_test register are not requ ired as long as the minimum time period is met. note 6.1 this restriction is only applicable after a fast-forward operation has been completed and the rx_ffwd bit has been cleared. refer to section 3.13.1.1, "rec eive data fifo fast forward," on page 60 for more information. table 6.2 read after read timing rules after reading... wait for this many ns? or perform this many reads of byte_test? (assuming t cycle of 165ns) before reading... rx data fifo 165 1 rx_fifo_inf rx status fifo 165 1 rx_fifo_inf tx status fifo 165 1 tx_fifo_inf rx_drop 330 2 rx_drop rx_dp_ctrl 330 2 tx status fifo rx status fifo note 6.1
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet smsc LAN9215 125 revision 2.9 (03-01-12) datasheet 6.2 pio reads pio reads can be used to access csrs or rx data and rx/tx status fifos. in this mode, counters in the csrs are latched at the beginning of the read cycl e. read data is valid as indicated in the timing diagram. pio reads can be performed using chip select (ncs) or read enable (nrd). either or both of these control signals mu st go high between cycles for the period specified. note: some registers have restrictions on the ti ming of back-to-back, write-read and read-read cycles. note: the ?data bus? width is 16 bits note: a pio read cycle begins when both ncs and nrd are asserted . the cycle ends when either or both ncs and nrd are deasserted. they may be asserted and deasserted in any order. parameters t csh and t csl must be extended using wa it states to meet the t cycle minimum. figure 6.1 pio read cycle timing table 6.3 pio read timing symbol description min typ max units t cycle read cycle time 165 ns t csl ncs, nrd assertion time 32 ns t csh ncs, nrd deassertion time (see note below) 13 133 ns t csdv ncs, nrd valid to data valid 30 ns t asu address setup to ncs, nrd valid 0 ns t ah address hold time 0 ns t don data buffer turn on time 0 ns t doff data buffer turn off time 7 ns t doh data output hold time 0 ns data bus ncs, nrd a[ 7:1 ]
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet revision 2.9 (03-01-12) 126 smsc LAN9215 datasheet 6.3 pio burst reads in this mode, performance is improved by allo wing up to 16 wo rd read cycles back-to-back. pio burst reads can be performed using chip select (ncs ) or read enable (nrd). either or both of these control signals must go high between bursts for the period specified. note: the ?data bus? width is 16 bits note: a pio burst read cycle begins when both ncs and nrd are asserted. the cycle ends when either or both ncs and nrd are deasserted. they may be asserted and deasserted in any order. figure 6.2 pio burst read cycle timing table 6.4 pio burst read timing symbol description min typ max units t csh ncs, nrd deassertion time 13 ns t csdv ncs, nrd valid to data valid 30 ns t acyc address cycle time 165 t asu address setup to ncs, nrd valid 0 ns t adv address stable to data valid 40 t ah address hold time 0 ns t don data buffer turn on time 0 ns t doff data buffer turn off time 7 ns t doh data output hold time 0 ns data bus ncs, nrd a[ 7:5 ] a[ 4:1 ]
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet smsc LAN9215 127 revision 2.9 (03-01-12) datasheet 6.4 rx data fifo direct pio reads in this mode the upper address inputs are not decoded, and any read of the LAN9215 will read the rx data fifo. this mode is enabled when fifo_sel is driven high during a read access. this is normally accomplished by connecting the fifo_sel signal to high-order address line. this mode is useful when the host processor must increment it s address when accessing the LAN9215. timing is identical to a pio read, and the fifo_sel signal has the same timing characteristics as the address lines. note that address lines a[2:1] are stil l used, and address bits a[7:3] are ignored. note: the ?data bus? width is 16 bits. note: an rx data fifo direct pio read cycle begins when both ncs and nrd are asserted. the cycle ends when either or both ncs and nrd are de-asserted. they may be asserted and de- asserted in any order. parameters t csh and t csl must be extended using wait states to meet the t cycle minimum. figure 6.3 rx data fifo direct pio read cycle timing table 6.5 rx data fifo direct pio read timing symbol description min typ max units t cycle read cycle time 165 ns t csl ncs, nrd assertion time 32 ns t csh ncs, nrd deassertion time (see note below) 13 133 ns t csdv ncs, nrd valid to data valid 30 ns t asu address, fifo_sel setup to ncs, nrd valid 0 ns t ah address, fifo_sel hold time 0 ns t don data buffer turn on time 0 ns t doff data buffer turn off time 7 ns t doh data output hold time 0 ns data bus ncs, nrd fifo _ sel a [ 2:1]
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet revision 2.9 (03-01-12) 128 smsc LAN9215 datasheet 6.5 rx data fifo di rect pio burst reads in this mode the upper address inputs are not dec oded, and any burst read of the LAN9215 will read the rx data fifo. this mode is enabled when fifo_sel is driven high during a read access. this is normally accomplished by connecting the fifo_ sel signal to a high-order address line. this mode is useful when the host processor must increm ent its address when accessing the LAN9215. timing is identical to a pio burst read, and the fifo_sel signal has the same timing characteristics as the address lines. in this mode, performance is im proved by allowing an unlimited nu mber of back-to-back read cycles. rx data fifo direct pio burst reads can be per formed using chip select (ncs) or read enable (nrd). when either or both of these control signals go high, they must remain high for the period specified. note that address lines a[2:1] are stil l used, and address bits a[7:3] are ignored. note: the ?data bus? width is 16 bits. note: an rx data fifo direct pio burst read cycle begins when both ncs and nrd are asserted. the cycle ends when either or bo th ncs and nrd are deasserted. they may be asserted and deasserted in any order. figure 6.4 rx data fifo direct pio burst read cycle timing table 6.6 rx data fifo dir ect pio burst read cycle timing symbol description min typ max units t csh ncs, nrd deassertion time 13 ns t csdv ncs, nrd valid to data valid 30 ns t acyc address cycle time 165 t asu address, fifo_sel setup to ncs, nrd valid 0 ns t adv address stable to data valid 40 t ah address, fifo_sel hold time 0 ns t don data buffer turn on time 0 ns t doff data buffer turn off time 7 ns t doh data output hold time 0 ns data bus ncs, nrd fifo _ sel a [ 2:1]
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet smsc LAN9215 129 revision 2.9 (03-01-12) datasheet 6.6 pio writes pio writes are used for all LAN9215 write cycles. pio writes can be performed using chip select (ncs) or write enable (nwr). either or both of these control signals must go high between cycles for the period specified. note: the ?data bus? width is 16 bits. note: a pio write cycle begins when both ncs and nwr are asserted. the cycle ends when either or both ncs and nwr are deasserted. they may be asserted and deasserted in any order. parameters t csh and t csl must be extended using wa it states to meet the t cycle minimum. figure 6.5 pio write cycle timing table 6.7 pio write cycle timing symbol description min typ max units t cycle write cycle time 165 ns t csl ncs, nwr assertion time 32 ns t csh ncs, nwr deassertion time (see note below) 13 133 ns t asu address setup to ncs, nwr assertion 0 ns t ah address hold time 0 ns t dsu data setup to ncs, nwr deassertion 7 ns t dh data hold time 0 ns data bus ncs, nwr a [ 7:1 ]
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet revision 2.9 (03-01-12) 130 smsc LAN9215 datasheet 6.7 tx data fifo direct pio writes in this mode the upper address inputs are not dec oded, and any write to the LAN9215 will write the tx data fifo. this mode is enabled when fifo_ sel is driven high during a write access. this is normally accomplished by connecting the fifo_sel signal to a high-order address line. this mode is useful when the host processor must increment it s address when accessing the LAN9215. timing is identical to a pio write, and the fifo_sel signal has the same timing characteristics as the address lines. note: the ?data bus? width is 16 bits. note: a tx data fifo direct pio write cycle begins when both ncs and nw r are asserted. the cycle ends when either or bo th ncs and nwr are deasserted . they may be asserted and deasserted in any order. parameters t csh and t csl must be extended using wait states to meet the t cycle minimum. figure 6.6 tx data fifo direct pio write timing table 6.8 tx data fifo direct pio write timing symbol description min typ max units t cycle write cycle time 165 ns t csl ncs, nwr assertion time 32 ns t csh ncs, nwr deassertion time (see note below) 13 133 ns t asu address, fifo_sel setup to ncs, nwr assertion 0 ns t ah address, fifo_sel hold time 0 ns t dsu data setup to ncs, nwr deassertion 7 ns t dh data hold time 0 ns data bus ncs, nwr fifo _ sel a [ 2:1 ]
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet smsc LAN9215 131 revision 2.9 (03-01-12) datasheet 6.8 reset timing figure 6.7 reset timing table 6.9 reset timing parameter description min typ max units notes t6.1 reset pulse width 200 us t6.2 configuration input setup to nreset rising 200 ns t6.3 configuration input hold after nreset rising 10 ns t6.4 output drive after nreset rising 16 ns t6.1 t6.2 t6.3 nreset configuration signals output drive t6.4
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet revision 2.9 (03-01-12) 132 smsc LAN9215 datasheet 6.9 eeprom timing the following specifies the eeprom ti ming requirements for the LAN9215: figure 6.8 eeprom timing table 6.10 eeprom timing values symbol description min typ max units t ckcyc eeclk cycle time 1110 1130 ns t ckh eeclk high time 550 570 ns t ckl eeclk low time 550 570 ns t cshckh eecs high before rising edge of eeclk 1070 ns t cklcsl eeclk falling edge to eecs low 30 ns t dvckh eedio valid before rising edge of eeclk (output) 550 ns t ckhdis eedio disable after rising edge eeclk (output) 550 ns t dsckh eedio setup to rising edge of eeclk (input) 90 ns t dhckh eedio hold after rising edge of eeclk (input) 0ns t ckldis eeclk low to data disable (output) 580 ns t cshdv eedio valid after eecs high (verify) 600 ns t dhcsl eedio hold after eecs low (verify) 0 ns t csl eecs low 1070 ns
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet smsc LAN9215 133 revision 2.9 (03-01-12) datasheet chapter 7 operational characteristics 7.1 absolute maximum ratings* supply voltage (vdd_a, vdd_ref, vreg, vdd_io) ( note 7.1 ). . . . . . . . . . . . . . . .0v to +3.3v+10% positive voltage on signal pins, with respect to ground ( note 7.2 ) . . . . . . . . . . . . . . . . . . . . . . . . . . +6v negative voltage on signal pins, with respect to ground ( note 7.3 ) . . . . . . . . . . . . . . . . . . . . . . . . -0.5v positive voltage on xtal1/clkin, with respect to ground . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . +4.6v positive voltage on xtal2, with respect to ground . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . +2.5v ambient operating temperature in still air (t a ). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 0 o c to +70 o c storage temperature. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .-65 o c to +150 o c lead temperature range . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . refer to jedec spec. j-std-020 hbm esd performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..+/- 5kv note 7.1 when powering this device from laboratory or system power supplies, it is important that the absolute maximum ratings not be exceeded or device failure can result. some power supplies exhibit voltage spikes on their outputs when ac power is switched on or off. in addition, voltage transients on the ac power line may appear on the dc output. if this possibility exists, it is suggeste d that a clamp circuit be used. note 7.2 this rating does not apply to the following pins: xtal1/clkin, xtal2, exres1. note 7.3 this rating does not apply to the following pins: exres1. *stresses exceeding those listed in this section c ould cause permanent damage to the device. this is a stress rating only. exposure to absolute maximum rating conditions for extended periods may affect device reliability. functional operation of the device at any condition exceeding those indicated in section 7.2, "operating conditions**" , section 7.6, "dc electr ical specifications" , or any other applicable section of this sp ecification is not implied. 7.2 operating conditions** supply voltage (vdd_a, vdd_ref, vreg, vdd_io) . . . . . . . . . . . . . . . . . . . . . . . . . . +3.3v +/- 10% ambient operating temperature in still air (t a ). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 0 o c to +70 o c note: do not drive input signals withou t power supplied to the device. note: apply and remove power to all power supply pins simultaneously, including the ethernet magnetics. do not apply power to indi vidual supply pins without the others. **proper operation of the LAN9215 is guaranteed only within the ran ges specified in this section.
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet revision 2.9 (03-01-12) 134 smsc LAN9215 datasheet 7.3 power consumption (device only) this section provides typical power consumpt ion values for the LAN9215 in various modes of operation. these measurements were taken under the following conditions: temperature: ................................................................................................................... ................ +25 c device vdd:.................................................................................................................... ............... +3.30v note: power dissipation is determined by operating fr equency, temperature, and supply voltage, as well as external source/sink requirements. note 7.4 d0 = normal operation, d1 = wol (wake on lan mode), d2= low power energy detect. table 7.1 power consumption device only mode total power - typical (mw) 10base-t operation d0, 10base-t /w traffic 282 d0, idle 289 d1, idle 177 d2, energy detect power down 65 d2, general power down 11 100base-tx operation d0, 100base-tx /w traffic 402 d0, idle 439 d1, idle 301 d2, energy detect power down (cable disconnected) 65 d2, general power down 11
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet smsc LAN9215 135 revision 2.9 (03-01-12) datasheet 7.4 power consumption (device and system components) this section provides typical pow er consumption values for a comp lete ethernet interface based on the LAN9215, including the power dissipated by the magnetics and other passive components. please refer to the smsc application note an14.9 - ?migrating from lan9115 to the LAN9215?, that can be found on smsc?s web site www.smsc.com, wh ich contains additional details on magnetics and other components used. note: the power measurements list below were taken under the following conditions: temperature: ................................................................................................................... ................ +25 c device vdd:.................................................................................................................... ............... +3.30v note: power dissipation is determined by operating fr equency, temperature, and supply voltage, as well as external source/sink requirements. table 7.2 power consumption device and system components mode total power - typical (mw) 10base-t operation d0, 10base-t /w traffic 612 d0, idle 620 d1, idle 508 d2, energy detect power down 65 d2, general power down 11 100base-tx operation d0, 100base-tx /w traffic 540 d0, idle 577 d1, idle 439 d2, energy detect power down 65 d2, general power down 11
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet revision 2.9 (03-01-12) 136 smsc LAN9215 datasheet 7.5 worst case current consumption this section details the worst case current cons umption for each device pow er supply. these values are provided to assist system designers with proper power supply design. these values cannot be used to determine typical power consumption of the device. note: the current measurements listed below were taken under the following conditions: temperature: ................................................................................................................... .....0 o c to +70 o c device vdd:.................................................................................................................. + 3.30 v +/- 10% note: current consumption is determined by operat ing frequency, temperature, and supply voltage, as well as external source/sink requirements. note: above values do not include the supply current for the magnetics. based on the recommended implementation, the maximum supply curr ent needed for the magnetics is 108ma. table 7.3 maximum supply current characteristics parameter supply name max units notes internal regulator supply current vreg 69 ma +3.3v i/o supply current vdd_io 13 ma +3.3v analog supply current vdd_a 40 ma reference supply current vdd_ref 31 ma
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet smsc LAN9215 137 revision 2.9 (03-01-12) datasheet 7.6 dc electri cal specifications this section details the dc electrical specific ations of the LAN9215 i /o buffers. the electrical specifications in this section are valid over t he voltage range and the temperature range specified in section 7.2, "operating conditions**" . table 7.4 i/o buffer characteristics parameter symbol min typ max units notes i type input buffer low input level v ili -0.3 0.8 v high input level v ihi 2.0 5.5 v input leakage (v in = gnd_io or vdd_io) i ih -10 10 ua note 7.5 input leakage (v in = 5.5v) i ih 107 ua note 7.5 , note 7.6 input capacitance c in 3.3 pf is type input buffer low input level v ili -0.3 v high input level v ihi 5.5 v negative-going threshold v ilt 1.01 1.18 1.35 v schmitt trigger positive-going threshold v iht 1.39 1.6 1.8 v schmitt trigger schmitt trigger hysteresis (v iht - v ilt ) v hys 345 420 485 mv input leakage (v in = gnd_io or vdd_io) i ih -10 10 ua note 7.5 input leakage (v in = 5.5v) i ih 107 ua note 7.5 , note 7.6 input capacitance c in 3.3 pf o12 type buffer low output level v ol 0.4 v i ol = 12ma high output level v oh vdd - 0.4 v i oh = -12ma od12 type buffer low output level v ol 0.4 v i ol = 12ma od8 type buffer low output level v ol 0.4 v i ol = 8ma o8 type buffer low output level v ol 0.4 v i ol = 8ma high output level v oh vdd - 0.4 v i oh = -8ma
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet revision 2.9 (03-01-12) 138 smsc LAN9215 datasheet note 7.5 this specification applies to all inputs and tri-stated bi-directional pins. internal pull-down and pull-up resistors add +/- 50ua per-pin (typical). note 7.6 this is the total v in input leakage for the entire device. this value should be divided by the number of pins driven to v in max to calculate per-pin leakage. for example, if 10 pins are driven to the maximum operational limit for v in , the per-pin input leakage is the maximum input leakage current divided by 10. note 7.7 measured at the line side of the transformer, line replaced by 100 (+/- 1%) resistor. note 7.8 offset from16 ns pulse width at 50% of pulse peak note 7.9 measured differentially. note 7.10 measured at the line side of the transformer, line replaced by 100 (+/- 1%) resistor. iclk input buffer low input level v ilck -0.3 0.5 v high input level v ihck 1.4 3.6 v table 7.5 100base-tx transceiver characteristics parameter symbol min typ max units notes peak differential output voltage high v pph 950 - 1050 mvpk note 7.7 peak differential output voltage low v ppl -950 - -1050 mvpk note 7.7 signal amplitude symmetry v ss 98 - 102 % note 7.7 signal rise & fall time t rf 3.0 - 5.0 ns note 7.7 rise & fall time symmetry t rfs --0.5ns note 7.7 duty cycle distortion d cd 35 50 65 % note 7.8 overshoot & undershoot v os --5% jitter 1.4 ns note 7.9 table 7.6 10base-t transceiver characteristics parameter symbol min typ max units notes transmitter peak differential output voltage v out 2.2 2.5 2.8 v note 7.10 receiver differential squelch threshold v ds 300 420 585 mv table 7.4 i/o buffer characteristics (continued) parameter symbol min typ max units notes
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet smsc LAN9215 139 revision 2.9 (03-01-12) datasheet 7.7 clock circuit the LAN9215 can accept either a 25mhz crystal (p referred) or a 25 mhz single-ended clock oscillator ( 50 ppm) input. the LAN9215 shares the 25mhz clock oscillator input (clkin) with the crystal input xtal1/clkin. if the single-ended clock oscillator method is implemented, xtal2 should be left unconnected and clkin should be driven with a nomi nal 0-3.3v clock signal. the input clock duty cycle is 40% minimum, 50% typical and 60% maximum. it is recommended that a crystal utilizing matching parallel load capacitors be used for the LAN9215 crystal input/output signals (xtal1, xtal2). see table 7.7, "LAN9215 crystal specifications" for crystal specifications. refer to application note an10 .7 - ?parallel crystal circuit input voltage control? for additional information. note 7.11 the maximum allowable values for frequency tolerance and frequency stability are application dependant. since any particular application must meet the ieee +/-50 ppm total ppm budget, the combination of these tw o values must be approximately +/-45 ppm (allowing for aging). note 7.12 frequency deviation over time is also referred to as aging. note 7.13 the total deviation for the transmitter clock frequency is specified by ieee 802.3u as +/- 50 ppm. note 7.14 this number includes the pad, the bond wire and the lead frame. pcb capacitance is not included in this value. the xtal1/clkin and xtal2 pin and pcb capacitance values are required to accurately calculate the value of the two external load capacitors. these two external load capacitors determine th e accuracy of the 25.000 mhz frequency. table 7.7 LAN9215 crystal specifications parameter symbol min nom max units notes crystal cut at, typ crystal oscillation mode fundamental mode crystal calibration mode parallel resonant mode frequency f fund - 25.000 - mhz frequency tolerance @ 25 o cf tol - - +/-50 ppm note 7.11 frequency stability over temp f temp - - +/-50 ppm note 7.11 frequency deviation over time f age - +/-3 to 5 - ppm note 7.12 total allowable ppm budget - - +/-50 ppm note 7.13 shunt capacitance c o -7 typ-pf load capacitance c l - 20 typ - pf drive level p w 300 - - uw equivalent series resistance r 1 --50ohm operating temperature range 0 - +70 o c LAN9215 xtal1/clkin pin capacitance -3 typ-pf note 7.14 LAN9215 xtal2 pin capacitance -3 typ-pf note 7.14
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet revision 2.9 (03-01-12) 140 smsc LAN9215 datasheet chapter 8 package outline 8.1 100-tqfp package notes: 1. controlling unit: millimeter. 2. tolerance on the true position of the leads is 0.04 mm maximum. 3. package body dimensions d1 and e1 do not include the mold protrusion. maximum mold protrusion is 0.25 mm. 4. dimension for foot length l measured at the gauge plane 0.25 mm ab ove the seating plane. 5. details of pin 1 identifier are optional but must be located within the zone indicated. figure 8.1 100 pin tqfp package definition table 8.1 100 pin tqfp package parameters min nominal max remarks a ~ ~ 1.60 overall package height a1 0.05 ~ 0.15 standoff a2 1.35 ~ 1.45 body thickness d 15.80 ~ 16.20 x span d1 13.90 ~ 14.10 x body size e 15.80 ~ 16.20 y span e1 13.90 ~ 14.10 y body size h 0.09 ~ 0.20 lead frame thickness l 0.45 0.60 0.75 lead foot length l1 ~ 1.00 ~ lead length e 0.50 basic lead pitch q0 o ~7 o lead foot angle w 0.17 0.22 0.27 lead width r1 0.08 ~ ~ lead shoulder radius r2 0.08 ~ 0.20 lead foot radius ccc ~ ~ 0.08 coplanarity
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet smsc LAN9215 141 revision 2.9 (03-01-12) datasheet 8.2 100-lfbga package notes: 1. all dimensions are in millimeters. 2. maximum radial true position tolerance of each ba ll is +/- 0.075mm at maximum material condition. dimension ?b? is measured at the maximum bal l diameter, parallel to primary datum ?c?. 3. primary datum ?c? (seating plane) is defined by the spherical crowns of the contact balls. 4. the a1 corner identifier may vary, but is always located within the zone indicated. figure 8.2 100 ball lfbg a package definition table 8.2 100 ball lfbga package parameters min nominal max remarks a ~ 1.60 1.70 overall package height a1 0.25 0.34 ~ standoff a2 1.16 1.26 1.36 package body thickness d/e 9.90 10.00 10.10 ove rall package size b 0.40 ~ 0.50 ball diameter e 0.80 basic ball pitch ccc ~ ~ 0.20 coplanarity
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet revision 2.9 (03-01-12) 142 smsc LAN9215 datasheet figure 8.3 100 ball lfbga recommended pcb land pattern
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet smsc LAN9215 143 revision 2.9 (03-01-12) datasheet chapter 9 datasheet revision history table 9.1 customer revision history revision level & date secti on/figure/entr y correction rev. 2.9 (03-01-12) section 5.4.8, "flow?flow control register," on page 109 updated pass control frames (bit 2) description to ?when set, the mac will pass the pause frame to the host...? rev. 2.8 (07-14-11) table 2.5, ?system and power signals,? on page 19 nled1 description modified to indicate that the signal is driven low when operating speed is 100mbs and is driven high during autonegotiation, when the cable is disconnected, and during 10 mbs operation. section 5.2.1, "rx fifo ports," on page 74 rx data fifo port is aliased to 16 word locations, not 16 dword locations. section 5.2.2, "tx fifo ports," on page 74 tx data fifo port is aliased to 16 word locations, not 16 dword locations. rev. 2.7 (03-15-10) chapter 2, "pin description and configuration," on page 15 added pin 1 designator to pin diagram section 7.2, "operating conditions**," on page 133 added note: ?do not drive input signals without power supplied to the device.? section 7.2, "operating conditions**," on page 133 added note: ?apply and remove power to all power supply pins simultaneously, including the ethernet magnetics. do not apply power to individual supply pins without the others.? rev. 2.5 (11-13-08) section 7.6, "dc electrical specifications," on page 137 added max input capacitance numbers rev. 2.4 (10-24-08) all fixed various typos section 3.7, "general purpose timer (gp timer)," on page 34 changed incorrect ?gpt_cnt? reference to ?gpt_load?: ?on a reset, or when the timer_en bit changes from set ?1? to cleared ?0,? the gpt_load field is initialized to ffffh.? section 5.3.23, "e2p_cmd ? eeprom command register," on page 98 corrected mac address loaded (bit 8) type from ?ro? to ?r/wc? table 7.7 on page 139 updated crystal specifications: drive level: 300uw esr: 50 ohms. rev. 2.3 (07-30-08) block diagram figure modified removing ?system memory? and double-sided arrow on top of the ?processor? block. rev. 2.3 (08-18-08) note 7.6 on page 138 note following i/o buffer characteristics table modified: changed from: ".....the per-pin input leakage is 10 divided by the maximum input leakage current." to: ".....the per-pin input leakage is the maximum input leakage current divided by 10."
16-bit non-pci 10/100 ethernet controller with hp auto-mdix support datasheet revision 2.9 (03-01-12) 144 smsc LAN9215 datasheet rev. 2.2 (06-19-08) figure 1.2, "internal block diagram" diagram redone. the second pll regulator was added to the diagram. the word ?core? was added to the regulator block title. added note to vdd_core/vdd18core and vdd_pll that states ?these pins must not be used to supply power to other external devices.? rev. 2.2 (06-10-08) auto-negotiation advertisement on page 115 bits 9 and 15 relabeled as reserved, read-only (ro), with a default of 0. auto-negotiation advertisement on page 115 fixed definition of bits 11:10 when equal to ?11? by adding ?advertise support for..? to beginning of definition. also added note stating ?when both symmetric pause and asymmetric pause support are advertised, the device will only be configured to, at most, one of the two settings upon auto-negotiation completion.? section 3.5, "wake-up frame detection," on page 30 and section 5.4.1, "mac_cr?mac control register," on page 102 added note: ?when wake-up frame detection is enabled via the wuen bit of the wucsr?wake- up control and status register , a broadcast wake- up frame will wake-up the device despite the state of the disable broadcast frame (bcast) bit in the mac_cr?mac control register .? section 5.4.12, "wucsr?wake-up control and status register," on page 111 fixed typo in bit 9: ?... mac address [1:0] bit set to 0.? was changed to ?...mac ad dress [0] bit set to 0.? rev. 2.1 (05-13-08) section 1.1, "block diagram" removed the system memo ry block and arrow above the microprocessor/ microcontroller rev. 2.0 (04-11-08) section 7.6, "dc electrical specifications," on page 137 input leakage current values added rev. 1.92 (10-22-07) chapter 2 pin description and configurationon page 15 pin assignment information re-organized into separate table. chapter 2 pin description and configurationon page 15 , chapter 8, "package outline," on page 140 , cover, and ordering code 100-lfbga package option added. eeclk pin description in chapter 2 pin description and configurationon page 15 note added to eeclk pin description to indicate proper usage. table 9.1 customer revision history (continued) revision level & date secti on/figure/entr y correction

▲Up To Search▲

Price & Availability of LAN9215

	To Download LAN9215 Datasheet File
If you can't view the Datasheet, Please click here to try to view without PDF Reader .